All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Steve French <smfrench@gmail.com>
Cc: fstests@vger.kernel.org
Subject: Re: xfstest status on current kernels
Date: Thu, 13 Nov 2014 14:26:26 +1100	[thread overview]
Message-ID: <20141113032626.GA28565@dastard> (raw)
In-Reply-To: <CAH2r5mu40qp-m7qZTnbsCKORPn_YYdWGZti32WYPFAJMUs1fhw@mail.gmail.com>

On Wed, Nov 12, 2014 at 05:31:20PM -0600, Steve French wrote:
> Is there a list somewhere of the full set of xfstests that are
> expected to run (and presumably pass) on current Linux kernels for the
> local file systems (ext4, btrfs and/or xfs)?

No.

You should expect all supported tests in the auto group to run for a
given filesystem. i.e. "./check -g auto" should run all the tests a
given filesytem supports, there should be very few failures, and the
only tests that _notrun are tests that aren't supported by either
you kernel or filesystem config.

> I want to make sure that I don't accidentally ignore a test (e.g. test
> generic/003 doesn't run with a message " [not run] relatime not
> supported by the current kernel" and want to make sure I am not
> missing something).

You need to such things yourself and determine if the test should
have run for your given test configuration.

e.g. on XFS you'll get stuff like this if you run with CRCs enabled:

xfs/287 0s ... [not run] 16 bit project IDs not supported on /dev/vdb

because such filesystem only support 32 bit project IDs on disk.

Or if you are missing stuff in your kernel config:

xfs/279  [not run] scsi_debug module not found

Or you aren't running with special subsystems enabled:

xfs/300 1s ... [not run] SELinux not enabled

Or your hardware is lacking in functionality:

generic/260      [not run] FITRIM not supported on /dev/vdb

or test tools weren't built due to missing libraries:

generic/010      [not run] dbtest was not built for this platform

or the filesystem doesn't support the functionality being tested:

generic/024 1s ... [not run] fs doesn't support RENAME_NOREPLACE

All of these things are issues local to the setup being tested, and
so there really isn't a canonical list of what should or shouldn't
run...

> Obviously cifs/smb3 and nfs are not going to run all the tests that
> ext4, btrfs and xfs do but it is easy to leave a test out for the
> wrong reasons (build dependency etc.) so want to know the list that
> should run on a local Linux fs.

Tests should notrun if tests tools were not built due to missing
build dependencies.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2014-11-13  3:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-12 23:31 xfstest status on current kernels Steve French
2014-11-13  3:26 ` Dave Chinner [this message]
2014-11-13  3:38   ` Steve French
2014-11-13  4:17     ` Eric Sandeen
2014-11-13  4:22     ` Dave Chinner
2014-11-13  4:33       ` Steve French
2014-11-13  4:44         ` Dave Chinner
2014-11-13  5:09           ` Steve French
2014-11-13  5:26             ` 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=20141113032626.GA28565@dastard \
    --to=david@fromorbit.com \
    --cc=fstests@vger.kernel.org \
    --cc=smfrench@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.