public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Eryu Guan <eguan@redhat.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH v2] fstests: add the missing _supported_fs to tests
Date: Thu, 9 Mar 2017 12:26:41 +0800	[thread overview]
Message-ID: <20170309042641.GH14226@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20170309021050.ulpsfpznr6ajd6e5@thunk.org>

On Wed, Mar 08, 2017 at 09:10:50PM -0500, Theodore Ts'o wrote:
> On Thu, Mar 09, 2017 at 01:42:57AM +0800, Eryu Guan wrote:
> > There're many tests that are missing _supported_fs check. I first
> > noticed this by running ext4/308 under an XFS test config by
> > accident then realized that there might be more tests missing
> > supported fs type check.
> 
> Stupid question --- I had assumed that all tests in xfs/* were
> implicitly xfs-only and all tests in btrfs/* were implicitly
> btrfs/only, and so on.  Is that not true?

Yes, that's true if you're not specifying tests on ./check command line.
But ./check still tries to run the tests given on command line. e.g.

	./check -s xfs ext4/308

This rarely happens so it's not a big issue. I just happened to hit it
and thought it'd be better to fix it :)

[Off topic] BTW, does the following patch look OK to you?

[PATCH] generic: require journal in shutdown tests

It skips shutdown tests on fs without journal, e.g. ext2 driving by ext4

Thanks,
Eryu

  reply	other threads:[~2017-03-09  4:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-08 11:54 [PATCH] ext4/308: add the missing _supported_fs Eryu Guan
2017-03-08 17:42 ` [PATCH v2] fstests: add the missing _supported_fs to tests Eryu Guan
2017-03-09  2:10   ` Theodore Ts'o
2017-03-09  4:26     ` Eryu Guan [this message]
2017-03-09  5:58       ` Theodore Ts'o

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=20170309042641.GH14226@eguan.usersys.redhat.com \
    --to=eguan@redhat.com \
    --cc=fstests@vger.kernel.org \
    --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