History

Shuhei Matsumoto 29e5c544c0 test/nvmf: Leave 2 seconds before starting the next shutdown test case

On the target side, disconnection process is asynchronous and ack is
sent to the initiator before completion.  This has caused latent
failure in a test case.  As a workaround, leave 2 seconds before
starting to the next test case for now.  Better solution will be
followed and so we don't care much about the location to insert
sleep.

Signed-off-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>
Change-Id: Id49349e3b7303ef9523b73d7a04d4e9837246c44
Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/479102
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Community-CI: SPDK CI Jenkins <sys_sgci@intel.com>
Community-CI: Broadcom SPDK FC-NVMe CI <spdk-ci.pdl@broadcom.com>
Reviewed-by: Changpeng Liu <changpeng.liu@intel.com>
Reviewed-by: Jim Harris <james.r.harris@intel.com>

2020-01-16 09:16:52 +00:00

host

test: eliminate case and suite from run_test

2019-12-24 08:24:42 +00:00

target

test/nvmf: Leave 2 seconds before starting the next shutdown test case

2020-01-16 09:16:52 +00:00

common.sh

test: Shellcheck - correct rule: Iterating over ls

2020-01-15 14:30:06 +00:00

nvmf.sh

test: move report_test_completion into run_test

2020-01-14 07:49:08 +00:00

README.md

test: add parse_common_script_args function

2019-05-22 23:43:51 +00:00

README.md

NVMe-oF test scripts

The test scripts in this directory hierarchy can be run in isolation by passing the --iso flag when running the test script. This will set up the RDMA NIC for testing and then tear it back down again when the test is completed.