public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfstests: remove tests 171, 172 and 173 from auto group
Date: Sat, 14 Feb 2009 13:13:05 -0600	[thread overview]
Message-ID: <499717C1.8080603@sandeen.net> (raw)
In-Reply-To: <20090214164127.GC19813@infradead.org>

Christoph Hellwig wrote:
> I don't have a single machine where these succeed, and due to the wait
> the filestreams allocator works these tests might depend on the phase
> on the moon to get their expected output.

ACK

> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> 
> Index: xfstests-dev/group
> ===================================================================
> --- xfstests-dev.orig/group	2009-02-14 15:13:08.000000000 +0000
> +++ xfstests-dev/group	2009-02-14 15:14:13.000000000 +0000
> @@ -273,9 +273,12 @@
>  168 dmapi auto
>  169 rw metadata auto
>  170 rw filestreams auto
> -171 rw filestreams auto
> -172 rw filestreams auto
> -173 rw filestreams auto
> +# the next three tests are not deterministic enough to get the
> +# "right" result on all platforms/configuration, so don't run
> +# them by default.
> +171 rw filestreams
> +172 rw filestreams
> +173 rw filestreams
>  174 rw filestreams auto
>  175 dmapi auto
>  176 dmapi auto
> 
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
> 

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

      reply	other threads:[~2009-02-14 19:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-14 16:41 [PATCH] xfstests: remove tests 171, 172 and 173 from auto group Christoph Hellwig
2009-02-14 19:13 ` Eric Sandeen [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=499717C1.8080603@sandeen.net \
    --to=sandeen@sandeen.net \
    --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