public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: Eryu Guan <guaneryu@gmail.com>,
	Amir Goldstein <amir73il@gmail.com>,
	fstests <fstests@vger.kernel.org>
Subject: Re: [PATCH] README: document the new default run mode
Date: Sun, 6 May 2018 09:37:32 +1000	[thread overview]
Message-ID: <20180505233732.GH10363@dastard> (raw)
In-Reply-To: <20180505222347.GO29205@thunk.org>

On Sat, May 05, 2018 at 06:23:47PM -0400, Theodore Y. Ts'o wrote:
> On Sat, May 05, 2018 at 10:09:11PM +0800, Eryu Guan wrote:
> > t
> > The 'dangerous' group and 'auto' group are not mutually exclusive when
> > it was introduced, see commit 3f28d55c3954 ("add freeze and dangerouss
> > groups"). But from previous discussions[1][2], they should be mutually
> > exclusive.
> 
> What might be nice is if there was some way to declare that a test is
> dangerous given a particular kernel version (or some combination of
> kernel version and file system type).  Right now I have to manually
> exclude tests when testing stable kernels, e.g.:
> 
> gce-xfstests full --kernel gs://gce-xfstests/bzImage-3.18 -X generic/269 -X ext4/022

That's what expunge files are for.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2018-05-05 23:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-05  0:19 [PATCH] README: document the new default run mode Dave Chinner
2018-05-05  6:55 ` Amir Goldstein
2018-05-05 14:09   ` Eryu Guan
2018-05-05 22:23     ` Theodore Y. Ts'o
2018-05-05 23:37       ` Dave Chinner [this message]
2018-05-05 23:36     ` Dave Chinner

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=20180505233732.GH10363@dastard \
    --to=david@fromorbit.com \
    --cc=amir73il@gmail.com \
    --cc=fstests@vger.kernel.org \
    --cc=guaneryu@gmail.com \
    --cc=tytso@mit.edu \
    /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