From: Bill O'Donnell <billodo@redhat.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: zlang@redhat.com, linux-xfs@vger.kernel.org,
fstests@vger.kernel.org, guan@eryu.me
Subject: Re: [PATCH 3/3] xfs/155: improve logging in this test
Date: Tue, 6 Jun 2023 21:24:15 -0500 [thread overview]
Message-ID: <ZH/qT1TPh0ghvji9@redhat.com> (raw)
In-Reply-To: <168609055958.2590724.15653702877825285667.stgit@frogsfrogsfrogs>
On Tue, Jun 06, 2023 at 03:29:19PM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <djwong@kernel.org>
>
> If this test fails after a certain number of writes, we should state
> the exact number of writes so that we can coordinate with 155.full.
> Instead, we state the pre-randomization number, which isn't all that
> helpful.
>
> Signed-off-by: Darrick J. Wong <djwong@kernel.org>
Makes sense.
Reviewed-by: Bill O'Donnell <bodonnel@redhat.com>
> ---
> tests/xfs/155 | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
>
> diff --git a/tests/xfs/155 b/tests/xfs/155
> index 25cc84069c..302607b510 100755
> --- a/tests/xfs/155
> +++ b/tests/xfs/155
> @@ -63,11 +63,12 @@ done
>
> # If NEEDSREPAIR is still set on the filesystem, ensure that a full run
> # cleans everything up.
> +echo "Checking filesystem one last time after $allowed_writes writes." >> $seqres.full
> if _check_scratch_xfs_features NEEDSREPAIR &> /dev/null; then
> echo "Clearing NEEDSREPAIR" >> $seqres.full
> _scratch_xfs_repair 2>> $seqres.full
> _check_scratch_xfs_features NEEDSREPAIR > /dev/null && \
> - echo "Repair failed to clear NEEDSREPAIR on the $nr_writes writes test"
> + echo "Repair failed to clear NEEDSREPAIR on the $allowed_writes writes test"
> fi
>
> # success, all done
>
prev parent reply other threads:[~2023-06-07 2:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 22:29 [PATCHSET 0/3] fstests: random fixes for v2023.05.28 Darrick J. Wong
2023-06-06 22:29 ` [PATCH 1/3] xfs/108: allow slightly higher block usage Darrick J. Wong
2023-06-07 1:51 ` Bill O'Donnell
2023-06-06 22:29 ` [PATCH 2/3] xfs/155: discard stderr when checking for NEEDSREPAIR Darrick J. Wong
2023-06-08 9:12 ` Andrey Albershteyn
2023-06-06 22:29 ` [PATCH 3/3] xfs/155: improve logging in this test Darrick J. Wong
2023-06-07 2:24 ` Bill O'Donnell [this message]
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=ZH/qT1TPh0ghvji9@redhat.com \
--to=billodo@redhat.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=guan@eryu.me \
--cc=linux-xfs@vger.kernel.org \
--cc=zlang@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox