From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: dsterba@suse.cz
Subject: [PATCH 2/3] btrfs-progs: test/fsck/020: Cleanup custom check function by overriding check_image function
Date: Fri, 10 Nov 2017 09:34:18 +0800 [thread overview]
Message-ID: <20171110013419.15159-2-wqu@suse.com> (raw)
In-Reply-To: <20171110013419.15159-1-wqu@suse.com>
Signed-off-by: Qu Wenruo <wqu@suse.com>
---
tests/fsck-tests/020-extent-ref-cases/test.sh | 13 ++++++-------
1 file changed, 6 insertions(+), 7 deletions(-)
diff --git a/tests/fsck-tests/020-extent-ref-cases/test.sh b/tests/fsck-tests/020-extent-ref-cases/test.sh
index 1e1e4e2386fb..f5c6591a92b8 100755
--- a/tests/fsck-tests/020-extent-ref-cases/test.sh
+++ b/tests/fsck-tests/020-extent-ref-cases/test.sh
@@ -19,12 +19,11 @@ source "$TOP/tests/common"
check_prereq btrfs
-for img in *.img *.raw.xz
-do
- image=$(extract_image "$img")
+check_image() {
+ local image
- # Since the return value bug is already fixed, we don't need
- # the old grep hack to detect bug.
+ image=$1
run_check "$TOP/btrfs" check "$image"
- rm -f "$image"
-done
+}
+
+check_all_images
--
2.15.0
next prev parent reply other threads:[~2017-11-10 1:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-10 1:34 [PATCH v2 1/3] btrfs-progs: test/fsck: Introduce test images containing tree reloc tree Qu Wenruo
2017-11-10 1:34 ` Qu Wenruo [this message]
2017-11-10 1:34 ` [PATCH 3/3] btrfs-progs: test/fsck/021: Cleanup custom check by overriding check_image Qu Wenruo
2017-11-27 19:02 ` [PATCH v2 1/3] btrfs-progs: test/fsck: Introduce test images containing tree reloc tree David Sterba
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=20171110013419.15159-2-wqu@suse.com \
--to=wqu@suse.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@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).