From: Eric Sandeen <sandeen@sandeen.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: Ben Myers <bpm@sgi.com>, xfs@oss.sgi.com
Subject: Re: xfstest failures
Date: Thu, 07 Nov 2013 07:24:28 -0600 [thread overview]
Message-ID: <527B948C.9060905@sandeen.net> (raw)
In-Reply-To: <20131107081710.GC25157@infradead.org>
On 11/7/13, 2:17 AM, Christoph Hellwig wrote:
> On Wed, Nov 06, 2013 at 12:20:47PM -0600, Eric Sandeen wrote:
>> that's right, it's a known bug w/ a testcase but no fix yet.
>>
>> I looked a bit, but ugh, xfsdump.
>
> Maybe it's time you come up with an xfail mechanism at least?
What's the proposal there, a "fail" group for things known to still
fail everywhere?
so i.e. ./check -x fail ? I can easily send a patch for that if
that's what folks want.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-11-07 13:24 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 [this message]
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
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=527B948C.9060905@sandeen.net \
--to=sandeen@sandeen.net \
--cc=bpm@sgi.com \
--cc=hch@infradead.org \
--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