From owner-freebsd-toolchain@FreeBSD.ORG Tue Oct 7 20:17:05 2014 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2AFB5668; Tue, 7 Oct 2014 20:17:05 +0000 (UTC) Received: from mail-yk0-x22e.google.com (mail-yk0-x22e.google.com [IPv6:2607:f8b0:4002:c07::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ABA619F2; Tue, 7 Oct 2014 20:17:04 +0000 (UTC) Received: by mail-yk0-f174.google.com with SMTP id 142so3175200ykq.33 for ; Tue, 07 Oct 2014 13:17:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=AsoxhWIvHrQ/FWUF6Nz89chVL1QbrrV4SgM3Hq6q4jg=; b=bFrFbxWyRS0RUYHLUdQvXQIhtcNp9kEVUnBr1dzpWhga9j0FxveWx9T0qG7NvBQ3au MXOQ5A0Hw46ZYvB3nhOAJEVWPGwQT2tEJv5GIGjA3TgmhBdXGt7GiIXD+M3I4RC27kOT EvpV0GiU8/05sJm/wroZMjPP6tPrnk6E+fCAoR3bdlWxP2MAx+CWU2jtYWKE7ey7lQPK z2RpTXGf43L7zvwCsYaQp9/PDSlIugAPBPYARBZWrNpua8FRRdJ6tMSc/+2gl7+XE42Y mVJjXlrhpaKwhep14wHRRe4mm3knWjzurMtE7eL2Vg/+oJTAaAf32hb5UOF3w8Il9FHM cwqg== MIME-Version: 1.0 X-Received: by 10.236.75.99 with SMTP id y63mr8461580yhd.105.1412713023722; Tue, 07 Oct 2014 13:17:03 -0700 (PDT) Sender: antoine.brodin.freebsd@gmail.com Received: by 10.170.207.73 with HTTP; Tue, 7 Oct 2014 13:17:03 -0700 (PDT) In-Reply-To: <543443CE.6000900@FreeBSD.org> References: <201410071915.s97JFrQo061043@svn.freebsd.org> <54343E60.7050208@FreeBSD.org> <543443CE.6000900@FreeBSD.org> Date: Tue, 7 Oct 2014 22:17:03 +0200 X-Google-Sender-Auth: _aoCqFNbCCoF55mm_TryCMCWMbM Message-ID: Subject: Re: 11-CURRENT redports builders miscompiling? From: Antoine Brodin To: Matthias Andree Content-Type: text/plain; charset=UTF-8 Cc: freebsd-toolchain@freebsd.org, FreeBSD Current X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Oct 2014 20:17:05 -0000 On Tue, Oct 7, 2014 at 9:49 PM, Matthias Andree wrote: > Am 07.10.2014 um 21:32 schrieb Antoine Brodin: >> On Tue, Oct 7, 2014 at 9:26 PM, Matthias Andree wrote: >>> Greetings, >>> >>> I have just updated sysutils/e2fsprogs and its slave ports(*), and test >>> drove them on redports. The self-test suite is failing on 11-CURRENT >>> i386 and amd64, but not on 10 or older releases. >>> >>> 11-amd64: https://redports.org/buildarchive/20141007190638-31576 >>> 11-i386: https://redports.org/buildarchive/20141007185700-4151 >>> >>> I am now wondering >>> - if there are issues with the toolchain on 11 that causes >>> miscompilation, or >>> - whether 11 is misbehaving on redports, or >>> - if e2fsprogs has code bugs that don't show on older toolchains. >> >> Hi, >> >> e2fsprogs version 1.42.10 tests were succeeding in a jail with a world >> from r272576 (1.5 day old) >> >> http://gohan2.ysv.freebsd.org/data/head-amd64-default-baseline/p370135_s272576/logs/e2fsprogs-1.42.10.log >> >> (this is poudriere, not tinderbox) > > Hi Antoine, > > merci for that. > > There are probably multiple changes, so if someone else can take the > newer 1.42.12 for a test on 11-current, either on a naked system or with > poudriere, that will be appreciated. What I find odd is that the > redports logs also show output deviations from expected, for instance, > here: > >> ==> /work/a/ports/sysutils/e2fsprogs/work/e2fsprogs-1.42.12/tests/r_resize_inode.failed <== >> --- r_resize_inode/expect 2014-08-25 03:08:16.000000000 +0000 >> +++ r_resize_inode.log 2014-10-07 19:10:00.000000000 +0000 >> @@ -1,7 +1,7 @@ >> mke2fs -q -F -O resize_inode -o Linux -b 1024 -g 1024 test.img 16384 >> resize2fs test.img 65536 >> Resizing the filesystem on test.img to 65536 (1k) blocks. >> -The filesystem on test.img is now 65536 (1k) blocks long. >> +The filesystem on test.img is now 65536 (1480342k) blocks long. >> >> Pass 1: Checking inodes, blocks, and sizes >> Pass 2: Checking directory structure > > The block size is bogus, and this happens on i386 and amd64 so is not > /obviously/ an issue of sizeof(long) or thereabouts. So, the test fail on head, but if you look carefully, 1480342*1024 = 0x5a5a... which looks like malloc junk. But when I turn off malloc debugging ( ln -s 'abort:false,junk:false' /etc/malloc.conf ) the tests succeed. So it looks like a bug in e2fsprogs. Cheers, Antoine