From: "Luis Henriques (SUSE)" <luis.henriques@linux.dev>
To: fstests@vger.kernel.org
Cc: "Luis Henriques (SUSE)" <luis.henriques@linux.dev>
Subject: [PATCH 2/2] ext4/006: take into account updates to _scratch_fuzz_modify()
Date: Thu, 14 Mar 2024 17:25:12 +0000 [thread overview]
Message-ID: <20240314172512.28293-3-luis.henriques@linux.dev> (raw)
In-Reply-To: <20240314172512.28293-1-luis.henriques@linux.dev>
Since function _scratch_fuzz_modify() has been updated, its output has
changed. Modify test ext4/006 to take this change into account.
Signed-off-by: Luis Henriques (SUSE) <luis.henriques@linux.dev>
---
tests/ext4/006 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/ext4/006 b/tests/ext4/006
index 8792167bd9c2..b73692aa5b81 100755
--- a/tests/ext4/006
+++ b/tests/ext4/006
@@ -131,7 +131,7 @@ echo "++ check fs (2)" >> $seqres.full
_check_scratch_fs >> $seqres.full 2>&1
grep -E -q '(did not fix|makes no progress)' $seqres.full && echo "e2fsck failed" | tee -a $seqres.full
-if [ "$(wc -l < "$ROUND2_LOG")" -ne 8 ]; then
+if [ "$(wc -l < "$ROUND2_LOG")" -ne 7 ]; then
echo "e2fsck did not fix everything" | tee -a $seqres.full
fi
echo "finished fuzzing" | tee -a "$seqres.full"
next prev parent reply other threads:[~2024-03-14 17:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 17:25 [PATCH 0/2] Ensure _scratch_fuzz_modify() works for other filesystems Luis Henriques (SUSE)
2024-03-14 17:25 ` [PATCH 1/2] common/fuzzy: make _scratch_fuzz_modify work for non-xfs filesystems Luis Henriques (SUSE)
2024-03-15 2:49 ` Darrick J. Wong
2024-03-14 17:25 ` Luis Henriques (SUSE) [this message]
2024-03-15 2:51 ` [PATCH 2/2] ext4/006: take into account updates to _scratch_fuzz_modify() Darrick J. Wong
2024-03-15 9:11 ` Luis Henriques
2024-03-15 15:37 ` 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=20240314172512.28293-3-luis.henriques@linux.dev \
--to=luis.henriques@linux.dev \
--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