From: Bart Van Assche <bvanassche@acm.org>
To: Omar Sandoval <osandov@fb.com>
Cc: linux-block@vger.kernel.org,
Johannes Thumshirn <jthumshirn@suse.de>,
Logan Gunthorpe <logang@deltatee.com>,
Bart Van Assche <bvanassche@acm.org>
Subject: [PATCH blktests 3/4] tests/nvmeof-mp/rc: Make the NVMeOF multipath tests more reliable
Date: Thu, 8 Aug 2019 13:05:05 -0700 [thread overview]
Message-ID: <20190808200506.186137-4-bvanassche@acm.org> (raw)
In-Reply-To: <20190808200506.186137-1-bvanassche@acm.org>
Fix the following failure for tests 002, 003, 004 and 011:
+tests/nvmeof-mp/rc: line 99: echo: write error: Operation already in progress
Signed-off-by: Bart Van Assche <bvanassche@acm.org>
---
tests/nvmeof-mp/rc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/nvmeof-mp/rc b/tests/nvmeof-mp/rc
index 7352b1628cd3..2493fcee12de 100755
--- a/tests/nvmeof-mp/rc
+++ b/tests/nvmeof-mp/rc
@@ -124,7 +124,7 @@ simulate_network_failure_loop() {
done 2>>"$FULL"
for ((i=0;i<5;i++)); do
- log_in && break
+ log_in 2>/dev/null && break
sleep 1
done
}
--
2.22.0.770.g0f2c4a37fd-goog
next prev parent reply other threads:[~2019-08-08 20:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-08 20:05 [PATCH blktests 0/4] Four blktests patches Bart Van Assche
2019-08-08 20:05 ` [PATCH blktests 1/4] tests/nvme/rc: Modify the approach for disabling and re-enabling Ctrl-C Bart Van Assche
2019-08-08 20:08 ` Logan Gunthorpe
2019-08-08 21:00 ` Bart Van Assche
2019-08-08 21:11 ` Logan Gunthorpe
2019-08-08 21:18 ` Bart Van Assche
2019-08-08 20:05 ` [PATCH blktests 2/4] tests/nvmeof-mp/rc: Make simulate_network_failure_loop() more robust Bart Van Assche
2019-08-08 20:05 ` Bart Van Assche [this message]
2019-08-08 20:05 ` [PATCH blktests 4/4] tests/srp/014: Add a test that triggers a SCSI reset while I/O is ongoing Bart Van Assche
2019-09-04 17:49 ` [PATCH blktests 0/4] Four blktests patches Bart Van Assche
2019-09-04 17:55 ` Omar Sandoval
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=20190808200506.186137-4-bvanassche@acm.org \
--to=bvanassche@acm.org \
--cc=jthumshirn@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=osandov@fb.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;
as well as URLs for NNTP newsgroup(s).