This test is static in nature and not dependent on actual nvmf setup that comes from the CI - everything is driven via a static json config that comes with the test itself. Instead, keep fuzzing directly in autotest.sh, under a top dedicated test flag SPDK_TEST_FUZZER - this should allow users to run only fuzzing part without touching the majority of the nvmf suite. Change-Id: I9c33c46e05f7c4b977b041673fe200d9d2989265 Signed-off-by: Michal Berger <michal.berger@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/14287 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Pawel Piatek <pawelx.piatek@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.