Currently we test both transports under perf each time we run the nvmf tests. Once we have created a jenkins job for the tcp transport, we will only need to run this test against the specified transport for each job. Change-Id: I053d11f4e6d6f4b86a3f29e6c8f43e1e196bedab Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/460714 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> |
||
---|---|---|
.. | ||
host | ||
target | ||
common.sh | ||
nvmf.sh | ||
README.md | ||
test_plan.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.