From: "Darrick J. Wong" <djwong@kernel.org>
To: Dave Chinner <david@fromorbit.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH 0/5]: CLI and feature improvements for check-parallel
Date: Tue, 14 Jan 2025 22:47:06 -0800 [thread overview]
Message-ID: <20250115064706.GD3557695@frogsfrogsfrogs> (raw)
In-Reply-To: <20250115062916.GC3557695@frogsfrogsfrogs>
On Tue, Jan 14, 2025 at 10:29:16PM -0800, Darrick J. Wong wrote:
> On Wed, Jan 15, 2025 at 04:51:11PM +1100, Dave Chinner wrote:
> > Hi folks,
> >
> > This patchset brings some new functionality to check-parallel to
> > make it easier to run across different machines and filesystems.
> > The patch seti adds these features:
> >
> > - auto-adjusts concurrency for the machine it is running on.
> > - adds CLI support of selection of tests. These CLI parameters are
> > identical to the check CLI parameters and the test lists are built
> > using the same code.
> > - adds support for logwrites devices so that all the test that use
> > dm-logwrites are now enabled
> > - adds support for specifying the initial filesystem type to test
> > on the CLI. This makes it easy to select xfs, btrfs, ext4, etc as
> > the target filesystem type that is to be tested.
> > - Only block device based filesystems can be used with
> > check-parallel, and this is now enforced at FSTYP selection time.
>
> Can you please add a --help so that curious users don't have to go find
> the calling conventions by reading the bash? :)
Oh, there is one in patch 3, please disregard this message.
--D
> --D
>
> > For example, testing the rw group on ext4 is now a simple matter of
> > adding the "-f ext4" parameter to the command line like so:
> >
> > $ time sudo ./check-parallel -D /mnt/xfs -f ext4 -g rw -x dump
> > Runner 12 Failures: ext4/308
> > Runner 1 Failures: generic/095
> > Runner 21 Failures: generic/042
> > Runner 51 Failures: generic/627
> > Runner 8 Failures: generic/032
> > Runner 13 Failures: generic/019
> > Runner 34 Failures: generic/347
> > .....
> >
> > Options like exclude files, groups and lists also work natively in
> > check-parallel now, same as they do in check...
> >
> > -Dave.
> >
>
next prev parent reply other threads:[~2025-01-15 6:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 5:51 [PATCH 0/5]: CLI and feature improvements for check-parallel Dave Chinner
2025-01-15 5:51 ` [PATCH 1/5] check-parallel: adjust concurrency according to CPU count Dave Chinner
2025-01-15 5:51 ` [PATCH 2/5] check: factor out test list building code Dave Chinner
2025-01-15 5:51 ` [PATCH 3/5] check-parallel: use common group list parsing code Dave Chinner
2025-01-15 5:51 ` [PATCH 4/5] check-parallel: add logwrite device support Dave Chinner
2025-01-15 5:51 ` [PATCH 5/5] check-parallel: allow FSTYP selection from the CLI Dave Chinner
2025-01-15 6:29 ` [PATCH 0/5]: CLI and feature improvements for check-parallel Darrick J. Wong
2025-01-15 6:47 ` Darrick J. Wong [this message]
2025-01-15 9:54 ` 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=20250115064706.GD3557695@frogsfrogsfrogs \
--to=djwong@kernel.org \
--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