From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: xfstest failures
Date: Thu, 7 Nov 2013 04:01:57 -0800 [thread overview]
Message-ID: <20131107120157.GA4683@infradead.org> (raw)
In-Reply-To: <20131107115722.GB11434@dastard>
On Thu, Nov 07, 2013 at 10:57:22PM +1100, Dave Chinner wrote:
> Actually, it doesn't. v4 configs give the same notrun output, which
> is wrong but doesn't result in a failure (hence I didn't notice it).
> Now that you've reported it I've just found a bug in the
> _requires_attr_v1 function that makes it always fail and notrun the
> test....
It fails for me running latests xfstests, latest xfsprogs an latest xfs
tree in a x86 VM running the default mkfs options.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-11-07 12:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 10:54 xfstest failures Christoph Hellwig
2013-11-06 16:18 ` Ben Myers
2013-11-06 18:20 ` Eric Sandeen
2013-11-07 8:17 ` Christoph Hellwig
2013-11-07 13:24 ` Eric Sandeen
2013-11-07 13:27 ` Christoph Hellwig
2013-11-07 13:46 ` Eric Sandeen
2013-11-07 13:48 ` Christoph Hellwig
2013-11-07 20:49 ` Ben Myers
2013-11-10 20:34 ` Dave Chinner
2013-11-10 20:33 ` Dave Chinner
2013-11-06 19:44 ` Dave Chinner
2013-11-06 19:58 ` Mark Tinguely
2013-11-07 8:16 ` Christoph Hellwig
2013-11-07 13:24 ` Mark Tinguely
2013-11-07 13:58 ` Eric Sandeen
2013-11-07 14:00 ` Christoph Hellwig
2013-11-07 14:02 ` Eric Sandeen
2013-11-07 20:59 ` Christoph Hellwig
2013-11-07 8:22 ` Christoph Hellwig
2013-11-07 11:57 ` Dave Chinner
2013-11-07 12:01 ` Christoph Hellwig [this message]
2013-11-07 12:23 ` Christoph Hellwig
2013-11-07 13:14 ` Markus Trippelsdorf
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=20131107120157.GA4683@infradead.org \
--to=hch@infradead.org \
--cc=david@fromorbit.com \
--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 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.