From: Wang Shilong <wangshilong1991@gmail.com>
To: fstests@vger.kernel.org
Subject: [PATCH v3] xfstests,shared/032: fix fsck failure
Date: Thu, 9 Oct 2014 20:16:57 -0400 [thread overview]
Message-ID: <1412900217-58174-1-git-send-email-wangshilong1991@gmail.com> (raw)
while running ./check tests/shared/032, it outputs something like:
FSTYP -- btrfs
PLATFORM -- Linux/x86_64 vm01 3.17.0-rc5+
MKFS_OPTIONS -- /dev/sdc
MOUNT_OPTIONS -- /dev/sdc /mnt/scratch
shared/032 2s ... 2s
_check_btrfs_filesystem: filesystem on /dev/sdc is inconsistent (see /root/xfstests-dev/results//shared/032.full)
Ran: shared/032
Passed all 1 tests
This is because xfstests will run fsck after each unit test,
for tests/shared/032, we have reformated SCRATCH_DEV to other fs,
fix this problem by skipping fsck here.
Signed-off-by: Wang Shilong <wangshilong1991@gmail.com>
---
v2->v3: fix commit message....
v1->v2: use _require_scratch_nocheck helper to skip fsck.(pointed by Eryu Guan)
---
tests/shared/032 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/shared/032 b/tests/shared/032
index 7835e30..a410003 100755
--- a/tests/shared/032
+++ b/tests/shared/032
@@ -40,7 +40,7 @@ rm -f $seqres.full
_supported_fs xfs btrfs
_supported_os Linux
-_require_scratch
+_require_scratch_nocheck
_require_no_large_scratch_dev
# mkfs.btrfs did not have overwrite detection at first
--
1.8.3.1
next reply other threads:[~2014-10-09 16:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 0:16 Wang Shilong [this message]
2014-10-09 16:26 ` [PATCH v3] xfstests,shared/032: fix fsck failure Eryu Guan
2014-10-09 16:28 ` Wang Shilong
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=1412900217-58174-1-git-send-email-wangshilong1991@gmail.com \
--to=wangshilong1991@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.