public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Tinguely <tinguely@sgi.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: xfstest failures
Date: Wed, 06 Nov 2013 13:58:31 -0600	[thread overview]
Message-ID: <527A9F67.6000208@sgi.com> (raw)
In-Reply-To: <20131106194417.GF6188@dastard>

On 11/06/13 13:44, Dave Chinner wrote:
> On Wed, Nov 06, 2013 at 02:54:51AM -0800, Christoph Hellwig wrote:
>> Unfortunately it seems our number of test failures is still through the
>> roof, mostly due to the lack of updates in xfstests for other changes.
>>
>> To start with the quick group in xfs I see:

...

>> xfs/206
>>
>> 	Does not expect the ftype flag.  Didn't we change a generic
>> 	filter to take care of this?
>
> xfs/206 has it's own mkfs filter:
>
> http://oss.sgi.com/archives/xfs/2013-10/msg00777.html
>
> I asked that the generic mkfs filters also be modified to support
> ftype, and there hasn't been any followup since then.
>

and I said that _filter_mkfs() does not need to be changed for field 
type. The standard output is correct already.

http://oss.sgi.com/archives/xfs/2013-10/msg00781.html

You also said the standard output is correct, and asked that new 
features add environment variables in _filter_mkfs():

http://oss.sgi.com/archives/xfs/2013-10/msg00823.html

Don't see any feature including crcs doing that yet.

--Mark.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2013-11-06 19:58 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 [this message]
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=527A9F67.6000208@sgi.com \
    --to=tinguely@sgi.com \
    --cc=david@fromorbit.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