From: Zorro Lang <zlang@redhat.com>
To: fstests@vger.kernel.org
Subject: [PATCH v5 2/2] xfs/068: skip new fsstress operations mwrite and mread
Date: Tue, 21 Mar 2017 17:18:03 +0800 [thread overview]
Message-ID: <1490087883-24453-2-git-send-email-zlang@redhat.com> (raw)
In-Reply-To: <1490087883-24453-1-git-send-email-zlang@redhat.com>
The output of x/068 will be perturbed by new fsstress operations.
For keep away breaking x/068's golden image, skip mread and
mwrite which are brought in by a new fsstress patch.
Reported-by: Eryu Guan <eguan@redhat.com>
Signed-off-by: Zorro Lang <zlang@redhat.com>
---
tests/xfs/068 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/xfs/068 b/tests/xfs/068
index 4dac95e..568ba60 100755
--- a/tests/xfs/068
+++ b/tests/xfs/068
@@ -44,7 +44,7 @@ _supported_fs xfs
_supported_os Linux
# need to ensure new fsstress operations don't perturb expected output
-FSSTRESS_AVOID="-f insert=0 $FSSTRESS_AVOID"
+FSSTRESS_AVOID="-f insert=0 -f mwrite=0 -f mread=0 $FSSTRESS_AVOID"
_create_dumpdir_stress_num 4096
_do_dump_restore
--
2.7.4
--
To unsubscribe from this list: send the line "unsubscribe fstests" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at https://urldefense.proofpoint.com/v2/url?u=http-3A__vger.kernel.org_majordomo-2Dinfo.html&d=DwIBAg&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=-yMrTV4jriXR7ieyzzjV-QgHBD0UDw8ixoR77aMeAHE&m=96dJ5wHk8dO6CXdf0pO5mLBQS3qWZv67us9m4CvqANI&s=YADzqekwOHb89zRff6FLwVTTaMuOYo19VrQRxUAm1ms&e=
next prev parent reply other threads:[~2017-03-21 9:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 9:18 [PATCH v5 1/2] fsstress: add mwrite/mread into test operation list Zorro Lang
2017-03-21 9:18 ` Zorro Lang [this message]
2017-03-21 10:55 ` [PATCH v5 2/2] xfs/068: skip new fsstress operations mwrite and mread Amir Goldstein
2017-03-21 21:34 ` Dave Chinner
2017-03-22 1:42 ` Amir Goldstein
2017-03-22 6:58 ` [PATCH v5 1/2] fsstress: add mwrite/mread into test operation list Eryu Guan
2017-03-22 14:59 ` Zorro Lang
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=1490087883-24453-2-git-send-email-zlang@redhat.com \
--to=zlang@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox