History

Konrad Sztyber d9f1d4e1dd test/nvmf: run bdevperf in the foreground There's no point in running bdevperf in the background only to send a framework_wait_init. Moreover, since bdevperf is executed with a 1s timeout, there's a risk that it'll finish before that RPC is sent causing a false positive failure. Fixes #2046 Signed-off-by: Konrad Sztyber <konrad.sztyber@intel.com> Change-Id: Icb5a8535d39954b7dfd3b4386cd008214d180bf3 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/11014 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Dong Yi <dongx.yi@intel.com>		2022-01-12 08:20:53 +00:00
..
host	bdev/nvme: add bdev_nvme_stop_discovery RPC	2022-01-12 08:20:23 +00:00
target	test/nvmf: run bdevperf in the foreground	2022-01-12 08:20:53 +00:00
common.sh	test: add iptables entry to forward packets across veth bridge	2022-01-10 15:23:39 +00:00
nvmf.sh	test: add nvmf/host/discovery.sh	2022-01-12 08:20:23 +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.