[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87mv1ie2v3.fsf@fastmail.com>
Date: Sat, 13 Jan 2018 06:37:04 +0100
From: Marius Bakke <mbakke@...tmail.com>
To: Theodore Ts'o <tytso@....edu>
Cc: linux-ext4@...r.kernel.org
Subject: Re: [PATCH e2fsprogs] tests: Fixup for new r_move_itable tests.
Theodore Ts'o <tytso@....edu> writes:
> On Sat, Nov 11, 2017 at 08:55:40AM +0100, Marius Bakke wrote:
>> Commits 257f009d1034737096f197dc875931207bcdfc75 and
>> 2b50c18a8a12781c26b71873f4368fe61711d9f9 missed one pass in expected
>> output.
>>
>> Signed-off-by: Marius Bakke <mbakke@...tmail.com>
>
> Hi, what architecture did you discover this on? I don't need this
> change on x86, but I was seeing some mysterious regression test
> failures on a big-endian system which seemed to look like this. I
> didn't have time to follow up on it then, but I suspect that this may
> be what you are running into.
Thanks for the reply. I get this on x86, but upon further
investigation, it only happens in the Guix build container.
Running "make check" interactively in a terminal works. Do you have any
idea what may cause these two tests to extend the inode table when run
in the isolated build chroot?
Download attachment "signature.asc" of type "application/pgp-signature" (488 bytes)
Powered by blists - more mailing lists