public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Eryu Guan <guaneryu@gmail.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Dave Chinner <david@fromorbit.com>, fstests <fstests@vger.kernel.org>
Subject: Re: [PATCH] README: document the new default run mode
Date: Sat, 5 May 2018 22:09:11 +0800	[thread overview]
Message-ID: <20180505140911.GE8373@desktop> (raw)
In-Reply-To: <CAOQ4uxgJ4+R05wfkgCA6DUEoQbPPJEhTGiE=5QDqoX5hjE7D7A@mail.gmail.com>

On Sat, May 05, 2018 at 09:55:54AM +0300, Amir Goldstein wrote:
> On Sat, May 5, 2018 at 3:19 AM, Dave Chinner <david@fromorbit.com> wrote:
> > From: Dave Chinner <dchinner@redhat.com>
> >
> > Also document the new way to run all tests (i.e. check -g all) and
> > clean up all the stray whitespace in the readme file.
> >
> > Signed-Off-By: Dave Chinner <dchinner@redhat.com>
> [...]
> > +      and it excludes tests that exercise conditions known to cause machine
> > +      failures (i.e. the "dangerous" tests).
> 
> That would have been nice.. if it was implemented...
> 
> I counted 22 dangerous tests, 20 of which are in auto group, unlike the
> 87 dangerous_* tests, none of which are in auto group.

The 'dangerous' group and 'auto' group are not mutually exclusive when
it was introduced, see commit 3f28d55c3954 ("add freeze and dangerous
groups"). But from previous discussions[1][2], they should be mutually
exclusive.

[1] https://www.spinics.net/lists/fstests/msg08652.html
[2] https://www.spinics.net/lists/fstests/msg08663.html

> 
> If running ./check would exclude 'dangerous' tests by default, should it
> also exclude dangerous_* tests? Or should we just remove the 20
> 'dangerous' tests from auto group and try not to add new auto&dangerous
> tests in the future?

I agreed, I think we should just remove the 20 'dangerous' tests from
auto group (AFAICT, they are not dangerous anymore). And I'll avoid
adding new tests that are in both dangerous & auto group.

Thanks,
Eryu

  reply	other threads:[~2018-05-05 14:09 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 [this message]
2018-05-05 22:23     ` Theodore Y. Ts'o
2018-05-05 23:37       ` Dave Chinner
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=20180505140911.GE8373@desktop \
    --to=guaneryu@gmail.com \
    --cc=amir73il@gmail.com \
    --cc=david@fromorbit.com \
    --cc=fstests@vger.kernel.org \
    /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