From: Zorro Lang <zlang@redhat.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: guaneryu@gmail.com, linux-xfs@vger.kernel.org,
fstests@vger.kernel.org, guan@eryu.me
Subject: Re: [PATCH 1/2] xfs/176: fix the group name
Date: Wed, 18 Aug 2021 11:02:02 +0800 [thread overview]
Message-ID: <20210818030202.h5ulaippfk33gas7@fedora> (raw)
In-Reply-To: <162924438548.779373.13859752576829414097.stgit@magnolia>
On Tue, Aug 17, 2021 at 04:53:05PM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <djwong@kernel.org>
>
> Filesystem shrink tests for xfs are supposed to be in the 'shrinkfs'
> group, not 'shrink'.
>
> Signed-off-by: Darrick J. Wong <djwong@kernel.org>
> ---
Yes, you're right:
[zorro@zlang-laptop xfstests-dev]$ grep -rsn _begin_fstest tests/|grep shrink
tests/xfs/176:11:_begin_fstest auto quick shrink
tests/xfs/163:13:_begin_fstest auto quick growfs shrinkfs
tests/xfs/168:14:_begin_fstest auto growfs shrinkfs ioctl prealloc stress
Reviewed-by: Zorro Lang <zlang@redhat.com>
> tests/xfs/176 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>
> diff --git a/tests/xfs/176 b/tests/xfs/176
> index ce9965c2..ba4aae59 100755
> --- a/tests/xfs/176
> +++ b/tests/xfs/176
> @@ -8,7 +8,7 @@
> # of the filesystem is now in the middle of a sparse inode cluster.
> #
> . ./common/preamble
> -_begin_fstest auto quick shrink
> +_begin_fstest auto quick shrinkfs
>
> # Import common functions.
> . ./common/filter
>
next prev parent reply other threads:[~2021-08-18 2:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 23:52 [PATCHSET 0/2] fstests: random fixes Darrick J. Wong
2021-08-17 23:53 ` [PATCH 1/2] xfs/176: fix the group name Darrick J. Wong
2021-08-18 3:02 ` Zorro Lang [this message]
2021-08-17 23:53 ` [PATCH 2/2] scsi_debug: fix module removal loop Darrick J. Wong
2021-08-18 3:55 ` Zorro Lang
2021-08-22 12:19 ` Eryu Guan
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=20210818030202.h5ulaippfk33gas7@fedora \
--to=zlang@redhat.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=guan@eryu.me \
--cc=guaneryu@gmail.com \
--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).