From: Luis Chamberlain <mcgrof@kernel.org>
To: fstests@vger.kernel.org, anand.jain@oracle.com,
aalbersh@redhat.com, djwong@kernel.org
Cc: linux-fsdevel@vger.kernel.org, kdevops@lists.linux.dev,
patches@lists.linux.dev, Luis Chamberlain <mcgrof@kernel.org>
Subject: [PATCH fstests 0/3] few enhancements
Date: Fri, 16 Feb 2024 10:18:56 -0800 [thread overview]
Message-ID: <20240216181859.788521-1-mcgrof@kernel.org> (raw)
This adds a couple of enhancements picked up over experiences with
kdevops. The first one is to augment the set of tests which are part of
the soak group. That required careful review of all of our tests, so
might as well update the tests with this information.
To allow us to verify this, we add an option to let us list the tests
which are part of a group with --list-group-tests. This came out of
recent discussions where Darrick proposed perhaps it might be possible
to query this [0], this is an attempt to help with that. The goal here
is to ensure that any test which does use SOAK_DURATION will be
agumented properly in the future as part of the soak group.
The last patch is a simple fstest watchdog enhacement which lets
applications monitoring only a guest's kernel buffer to know when
the show has started and ended. It is completely optional to use, but
kdevops has been using this in its own wrapper oscheck.sh for years now.
[0] https://lkml.kernel.org/r/20240125222956.GD6188@frogsfrogsfrogs
Luis Chamberlain (3):
tests: augment soak test group
check: add support for --list-group-tests
check: add --print-start-done to enhance watchdogs
check | 32 +++++++++++++++++++++++++++++++-
tests/generic/019 | 2 +-
tests/generic/388 | 2 +-
tests/generic/475 | 2 +-
tests/generic/642 | 2 +-
tests/generic/648 | 2 +-
tests/xfs/285 | 2 +-
tests/xfs/517 | 2 +-
tests/xfs/560 | 2 +-
tests/xfs/561 | 2 +-
tests/xfs/562 | 2 +-
tests/xfs/565 | 2 +-
tests/xfs/570 | 2 +-
tests/xfs/571 | 2 +-
tests/xfs/572 | 2 +-
tests/xfs/573 | 2 +-
tests/xfs/574 | 2 +-
tests/xfs/575 | 2 +-
tests/xfs/576 | 2 +-
tests/xfs/577 | 2 +-
tests/xfs/578 | 2 +-
tests/xfs/579 | 2 +-
tests/xfs/580 | 2 +-
tests/xfs/581 | 2 +-
tests/xfs/582 | 2 +-
tests/xfs/583 | 2 +-
tests/xfs/584 | 2 +-
tests/xfs/585 | 2 +-
tests/xfs/586 | 2 +-
tests/xfs/587 | 2 +-
tests/xfs/588 | 2 +-
tests/xfs/589 | 2 +-
tests/xfs/590 | 2 +-
tests/xfs/591 | 2 +-
tests/xfs/592 | 2 +-
tests/xfs/593 | 2 +-
tests/xfs/594 | 2 +-
tests/xfs/595 | 2 +-
tests/xfs/727 | 2 +-
tests/xfs/729 | 2 +-
tests/xfs/800 | 2 +-
41 files changed, 71 insertions(+), 41 deletions(-)
--
2.42.0
next reply other threads:[~2024-02-16 18:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 18:18 Luis Chamberlain [this message]
2024-02-16 18:18 ` [PATCH 1/3] tests: augment soak test group Luis Chamberlain
2024-02-16 18:18 ` [PATCH 2/3] check: add support for --list-group-tests Luis Chamberlain
2024-02-19 3:38 ` Dave Chinner
2024-02-21 16:45 ` Luis Chamberlain
2024-02-25 16:08 ` Zorro Lang
2024-02-16 18:18 ` [PATCH 3/3] check: add --print-start-done to enhance watchdogs Luis Chamberlain
2024-02-19 3:42 ` Dave Chinner
2024-02-21 16:46 ` Luis Chamberlain
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=20240216181859.788521-1-mcgrof@kernel.org \
--to=mcgrof@kernel.org \
--cc=aalbersh@redhat.com \
--cc=anand.jain@oracle.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=kdevops@lists.linux.dev \
--cc=linux-fsdevel@vger.kernel.org \
--cc=patches@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).