From: "Darrick J. Wong" <djwong@kernel.org>
To: djwong@kernel.org, guaneryu@gmail.com
Cc: Christoph Hellwig <hch@lst.de>,
linux-xfs@vger.kernel.org, fstests@vger.kernel.org, guan@eryu.me
Subject: [PATCH 3/9] xfs: fix incorrect fuzz test group name
Date: Wed, 15 Sep 2021 16:42:53 -0700 [thread overview]
Message-ID: <163174937390.380880.10714985927715519622.stgit@magnolia> (raw)
In-Reply-To: <163174935747.380880.7635671692624086987.stgit@magnolia>
From: Darrick J. Wong <djwong@kernel.org>
The group name for fuzz tests is 'fuzzers'.
Signed-off-by: Darrick J. Wong <djwong@kernel.org>
Reviewed-by: Christoph Hellwig <hch@lst.de>
---
tests/xfs/491 | 2 +-
tests/xfs/492 | 2 +-
tests/xfs/493 | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/tests/xfs/491 b/tests/xfs/491
index 5c7c5d1f..7402b09a 100755
--- a/tests/xfs/491
+++ b/tests/xfs/491
@@ -7,7 +7,7 @@
# Test detection & fixing of bad summary block counts at mount time.
#
. ./common/preamble
-_begin_fstest auto quick fuzz
+_begin_fstest auto quick fuzzers
# Import common functions.
. ./common/filter
diff --git a/tests/xfs/492 b/tests/xfs/492
index 8258e5d8..514ac1e4 100755
--- a/tests/xfs/492
+++ b/tests/xfs/492
@@ -7,7 +7,7 @@
# Test detection & fixing of bad summary inode counts at mount time.
#
. ./common/preamble
-_begin_fstest auto quick fuzz
+_begin_fstest auto quick fuzzers
# Import common functions.
. ./common/filter
diff --git a/tests/xfs/493 b/tests/xfs/493
index 58fd9c99..58091ad7 100755
--- a/tests/xfs/493
+++ b/tests/xfs/493
@@ -8,7 +8,7 @@
# Corrupt the AGFs to test mount failure when mount-fixing fails.
#
. ./common/preamble
-_begin_fstest auto quick fuzz
+_begin_fstest auto quick fuzzers
# Import common functions.
. ./common/filter
next prev parent reply other threads:[~2021-09-15 23:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 23:42 [PATCHSET v3 0/9] fstests: document all test groups Darrick J. Wong
2021-09-15 23:42 ` [PATCH 1/9] ceph: re-tag copy_file_range as being in the copy_range group Darrick J. Wong
2021-09-16 5:51 ` Amir Goldstein
2021-09-15 23:42 ` [PATCH 2/9] xfs: move reflink tests into the clone group Darrick J. Wong
2021-09-16 5:51 ` Amir Goldstein
2021-09-15 23:42 ` Darrick J. Wong [this message]
2021-09-16 5:52 ` [PATCH 3/9] xfs: fix incorrect fuzz test group name Amir Goldstein
2021-09-15 23:42 ` [PATCH 4/9] btrfs: fix incorrect subvolume " Darrick J. Wong
2021-09-16 5:52 ` Amir Goldstein
2021-09-15 23:43 ` [PATCH 5/9] generic/631: change this test to use the 'whiteout' group Darrick J. Wong
2021-09-16 5:53 ` Amir Goldstein
2021-09-15 23:43 ` [PATCH 6/9] tools: make sure that test groups are described in the documentation Darrick J. Wong
2021-09-16 5:58 ` Amir Goldstein
2021-09-15 23:43 ` [PATCH 7/9] tools: add missing license tags to my scripts Darrick J. Wong
2021-09-16 6:06 ` Amir Goldstein
2021-09-16 21:44 ` Darrick J. Wong
2021-09-15 23:43 ` [PATCH 8/9] new: only allow documented test group names Darrick J. Wong
2021-09-16 6:10 ` Amir Goldstein
2021-09-15 23:43 ` [PATCH 9/9] new: don't allow new tests in group 'other' Darrick J. Wong
2021-09-16 6:40 ` Amir Goldstein
2021-09-16 22:53 ` Darrick J. Wong
2021-09-17 2:31 ` Amir Goldstein
2021-09-17 16:00 ` Darrick J. Wong
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=163174937390.380880.10714985927715519622.stgit@magnolia \
--to=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=guan@eryu.me \
--cc=guaneryu@gmail.com \
--cc=hch@lst.de \
--cc=linux-xfs@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;
as well as URLs for NNTP newsgroup(s).