verify.state files are not very useful because we fail the tests at any first failure. If there was something wrong with IO verification then autotest.sh would fail. Fio files with metrics output (IOPS, BW, latency, etc) are also not very useful as per-patch tests are not focused on benchmarking. Fixes #2546 Signed-off-by: Kamil Godzwon <kamilx.godzwon@intel.com> Change-Id: I33fbe2fb0749d840f08ffe0d606d206268140991 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/13019 Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> |
||
---|---|---|
.. | ||
host | ||
target | ||
common.sh | ||
nvmf.sh | ||
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.