From: Dave Chinner <david@fromorbit.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfstests: add freeze and dangerous groups
Date: Mon, 5 Mar 2012 14:08:43 +1100 [thread overview]
Message-ID: <20120305030843.GB3592@dastard> (raw)
In-Reply-To: <4F50FBB1.1090107@redhat.com>
On Fri, Mar 02, 2012 at 10:56:17AM -0600, Eric Sandeen wrote:
> Add 2 new test groups:
>
> freeze: tests which test filesystem freeze
That's fine.
> dangerous: tests which may hang or oops
Hmmm.
> The 2nd may be useful for automated testing to do i.e.
>
> ./check -g auto -x dangerous
> ./check -g auto,dangerous
>
> to try to get fuller coverage before running into tests
> which may panic or hang the box and stop the test cycle.
>
> I doubt I have all the potential dangerous tests, but
> they can be added later when found.
>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
I'm not sure "dangerous" is a black and white status for a test.
What if the test doesn't cause problems for upstream, but causes
problems for older vendor kernels? Does that make it dangerous? e.g.
test 104 will hang a RHEL5.x kernel, but is perfectly safe on a
RHEL6.x kernel - does that make it dangerous? It seems that many of
the recent tests for specific regressions fall into this sort of
category. Indeed, how do we answer the question "when does a test no
longer be considered dangerous" or "what test is considered
dangerous for this kernel/platform"?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-03-05 3:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 16:56 [PATCH] xfstests: add freeze and dangerous groups Eric Sandeen
2012-03-05 3:08 ` Dave Chinner [this message]
2012-03-05 4:11 ` Eric Sandeen
2012-03-31 20:13 ` [PATCH] " Christoph Hellwig
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=20120305030843.GB3592@dastard \
--to=david@fromorbit.com \
--cc=sandeen@redhat.com \
--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