From: Dwight Engen <dwight.engen@oracle.com>
To: xfs@oss.sgi.com
Subject: [PATCH] xfstests: fix README, FSTYP options
Date: Tue, 25 Jun 2013 15:34:23 -0400 [thread overview]
Message-ID: <20130625153423.513e4074@oracle.com> (raw)
commit cbcc88fb changed test selection to use shell globs, so fixup the
examples given in the README file.
add options for FSTYPs supported by _scratch_mkfs().
Signed-off-by: Dwight Engen <dwight.engen@oracle.com>
---
README | 5 +++--
check | 4 +++-
2 files changed, 6 insertions(+), 3 deletions(-)
diff --git a/README b/README
index d4d4f31..af4e4a5 100644
--- a/README
+++ b/README
@@ -81,9 +81,10 @@ Running tests:
- cd xfstests
- By default the tests suite will run xfs tests:
- - ./check 001 002 003 ... or you can explicitly run a filesystem:
+ - ./check '*/001' '*/002' '*/003'
+ - ./check '*/06?'
+ - You can explicitly specify a filesystem (btrfs, ext4, nfs, udf, xfs):
./check -xfs [test(s)]
- - You can run a range of tests: ./check 067-078
- Groups of tests maybe ran by: ./check -g [group(s)]
See the 'group' file for details on groups
- for udf tests: ./check -udf [test(s)]
diff --git a/check b/check
index ff8fbcf..a677727 100755
--- a/check
+++ b/check
@@ -159,9 +159,11 @@ while [ $# -gt 0 ]; do
case "$1" in
-\? | -h | --help) usage ;;
+ -btrfs) FSTYP=btrfs ;;
+ -ext4) FSTYP=ext4 ;;
+ -nfs) FSTYP=nfs ;;
-udf) FSTYP=udf ;;
-xfs) FSTYP=xfs ;;
- -nfs) FSTYP=nfs ;;
-g) group=$2 ; shift ;
group_list=$(get_group_list $group)
--
1.8.1.4
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2013-06-25 19:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 19:34 Dwight Engen [this message]
2013-06-26 0:50 ` [PATCH] xfstests: fix README, FSTYP options Dave Chinner
2013-06-26 16:29 ` Dwight Engen
2013-06-27 15:57 ` [PATCH v2] " Dwight Engen
2013-07-09 16:11 ` Ben Myers
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=20130625153423.513e4074@oracle.com \
--to=dwight.engen@oracle.com \
--cc=xfs@oss.sgi.com \
/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