From: Marius Bakke <mbakke@fastmail.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH e2fsprogs] tests: Fixup for new r_move_itable tests.
Date: Sat, 13 Jan 2018 06:37:04 +0100 [thread overview]
Message-ID: <87mv1ie2v3.fsf@fastmail.com> (raw)
In-Reply-To: <20180111191327.GA5559@thunk.org>
[-- Attachment #1: Type: text/plain, Size: 925 bytes --]
Theodore Ts'o <tytso@mit.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@fastmail.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?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2018-01-13 5:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-11 7:55 [PATCH e2fsprogs] tests: Fixup for new r_move_itable tests Marius Bakke
2018-01-11 19:13 ` Theodore Ts'o
2018-01-13 5:37 ` Marius Bakke [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mv1ie2v3.fsf@fastmail.com \
--to=mbakke@fastmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.