Spdk/test/nvmf
Ben Walker 5dfd4f261f test/nvmf: Restart target between shutdown tests
For RDMA, it seems we may have to wait out some timeouts to
reset all of the connections to make this test work reliably. Instead,
just restart the target for each test.

If there's a way to force close all of the connections properly in the
future we can go back to running these all on a single target.

Change-Id: If79257349007765dc16bacebf810312a025d70a3
Signed-off-by: Ben Walker <benjamin.walker@intel.com>
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/1609
Community-CI: Broadcom CI
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>
Reviewed-by: Jim Harris <james.r.harris@intel.com>
Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com>
2020-04-14 11:32:35 +00:00
..
host test: do not use iter_pci_class_code in tests 2020-03-18 08:03:21 +00:00
target test/nvmf: Restart target between shutdown tests 2020-04-14 11:32:35 +00:00
common.sh test/nvmf: Don't let nvmfcleanup() to fail upon finishing the test 2020-04-10 07:08:43 +00:00
nvmf.sh test/nvmf: Add skel for nvmf error testing 2020-02-27 10:15:40 +00:00
README.md test: add parse_common_script_args function 2019-05-22 23:43:51 +00:00

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.