From: jeff.lien@wdc.com (Jeff Lien)
Subject: [PATCH] NVMe-CLI Fix command failures in regress script
Date: Fri, 2 Feb 2018 13:50:20 -0600 [thread overview]
Message-ID: <20180202195021.8560-1-jeff.lien@wdc.com> (raw)
Signed-off-by: Jeff Lien <jeff.lien at wdc.com>
---
regress | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/regress b/regress
index aa7820c..0278d1d 100755
--- a/regress
+++ b/regress
@@ -89,7 +89,7 @@ if $LIST ; then
run_test nvme list
fi
run_test nvme id-ctrl ${DEVICE}
-run_test nvme id-ns -raw-binary ${DEVICE}
+run_test nvme id-ns -n 1 -raw-binary ${DEVICE}
run_test nvme list-ns -n 1 ${DEVICE}
run_test nvme get-ns-id ${DEVICE}
run_test nvme get-log ${DEVICE} --log-id=2 --log-len=512
@@ -98,13 +98,13 @@ run_test nvme fw-log ${DEVICE} -b
run_test nvme smart-log ${DEVICE}
run_test nvme error-log ${DEVICE}
run_test nvme get-feature ${DEVICE} -f 7
-run_test nvme flush ${DEVICE}
+run_test nvme flush -n 1 ${DEVICE}
if $WRITE ; then
run_test dd if=/dev/urandom of=${RAND_WFILE} bs=${RAND_SIZE} count=1
- run_test nvme write ${DEVICE} --start-block=0 --block-count=0 --data-size=${RAND_SIZE} --data ${RAND_WFILE}
+ run_test nvme write ${DEVICE}n1 --start-block=0 --block-count=0 --data-size=${RAND_SIZE} --data ${RAND_WFILE}
fi
-run_test nvme read ${DEVICE} --start-block=0 --block-count=0 --data-size=${RAND_SIZE} --data ${RAND_RFILE} --latency
+run_test nvme read ${DEVICE}n1 --start-block=0 --block-count=0 --data-size=${RAND_SIZE} --data ${RAND_RFILE} --latency
if $WRITE ; then
run_test diff ${RAND_RFILE} ${RAND_WFILE}
rm ${RAND_WFILE} > /dev/null
--
2.14.2.746.g8fb8a94
next reply other threads:[~2018-02-02 19:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 19:50 Jeff Lien [this message]
2018-02-02 20:29 ` [PATCH] NVMe-CLI Fix command failures in regress script Keith Busch
2018-02-02 21:33 ` Jeffrey Lien
2018-02-02 21:38 ` Keith Busch
2018-02-05 16:49 ` Jeffrey Lien
2018-02-05 16:57 ` Keith Busch
2018-02-05 19:00 ` Jeffrey Lien
2018-02-05 19:34 ` Keith Busch
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=20180202195021.8560-1-jeff.lien@wdc.com \
--to=jeff.lien@wdc.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