From: Josef Bacik <jbacik@fb.com>
To: <linux-btrfs@vger.kernel.org>
Subject: [PATCH] Btrfs-progs: skip extent rebuild test if no testdev
Date: Fri, 3 Oct 2014 10:59:36 -0400 [thread overview]
Message-ID: <1412348376-6771-1-git-send-email-jbacik@fb.com> (raw)
It is highly obnoxious to have to go put in a testdev when all you really want
is to run the quick image tests. Make this part optional so if we don't have a
testdev specified we just don't run that particular test. Thanks,
Signed-off-by: Josef Bacik <jbacik@fb.com>
---
tests/fsck-tests.sh | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/tests/fsck-tests.sh b/tests/fsck-tests.sh
index b783b78..867366b 100644
--- a/tests/fsck-tests.sh
+++ b/tests/fsck-tests.sh
@@ -24,10 +24,6 @@ run_check()
rm -f $RESULT
-if [ -z $TEST_DEV ] || [ -z $TEST_MNT ];then
- _fail "please set TEST_DEV and TEST_MNT"
-fi
-
# test rely on corrupting blocks tool
run_check make btrfs-corrupt-block
@@ -45,6 +41,11 @@ do
run_check $here/btrfsck test.img
done
+if [ -z $TEST_DEV ] || [ -z $TEST_MNT ];then
+ echo " [NOTRUN] extent tree rebuild"
+ exit 0
+fi
+
# test whether fsck can rebuild a corrupted extent tree
test_extent_tree_rebuild()
{
--
1.8.3.1
reply other threads:[~2014-10-03 14:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1412348376-6771-1-git-send-email-jbacik@fb.com \
--to=jbacik@fb.com \
--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).