From: Ted Ts'o <tytso@mit.edu>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-ext4@vger.kernel.org, xfs@oss.sgi.com,
Stefan Behrens <sbehrens@giantdisaster.de>
Subject: Re: xfstests #62 broken on ext4
Date: Sat, 13 Aug 2011 20:44:17 -0400 [thread overview]
Message-ID: <20110814004417.GA3524@thunk.org> (raw)
In-Reply-To: <20110813201419.GA6442@infradead.org>
On Sat, Aug 13, 2011 at 04:14:19PM -0400, Christoph Hellwig wrote:
> On Sat, Aug 13, 2011 at 10:38:51AM -0400, Theodore Ts'o wrote:
> >
> > Xfstests #62 was recently enabled by commit b2b36d0a4.
> >
> > However, this test is failing for ext4 because ext4 doesn't support
> > extended attributes on anything other than regular files and
> > directories. This is behavior is documented in the attr(5) man page:
>
> As explained to you before that is not the reason why it fails. The
> reason is that Andreas Gruenbacher changed return values for certain
> xattr operations in commit 55b23bde19c08f14127a27d461a4e079942c7258.
Apologies, I hadn't yet read your mail message while I started digging
into this failure this morning, and the fact that the files got
reordered from what was expected in the output file confused me into
thinking ext4 was failing tests that where the 062.out file expected
successes, and I juped to conclusions.
I see there's an sort command at the very end of _extend_test_bed(), I
presume we should also add a similar "LC_COLLATE=POSIX sort" to the
other "find" command pipelines, and it's easy enough to filter out the
lost+found directory by adding a "! -name lost+found".
- Ted
next prev parent reply other threads:[~2011-08-14 0:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-13 14:38 xfstests #62 broken on ext4 Theodore Ts'o
2011-08-13 15:57 ` Stefan Behrens
2011-08-13 20:14 ` Christoph Hellwig
2011-08-14 0:44 ` Ted Ts'o [this message]
2011-08-14 16:09 ` Christoph Hellwig
2011-08-19 14:46 ` Eric Sandeen
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=20110814004417.GA3524@thunk.org \
--to=tytso@mit.edu \
--cc=hch@infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=sbehrens@giantdisaster.de \
--cc=xfs@oss.sgi.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).