Also, clear generated fuzz logs upon successful test run - they may get quite big (> 250MB) in size which doesn't play well with the artifacts limit CI enforces. If the test succeeded then there's no point in keeping them around for any potential debugging. Signed-off-by: Michal Berger <michal.berger@intel.com> Change-Id: I240e8217cd50dba258310604c6985d8f6a832756 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/15030 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Konrad Sztyber <konrad.sztyber@intel.com> Reviewed-by: Krzysztof Karas <krzysztof.karas@intel.com> Reviewed-by: Pawel Piatek <pawelx.piatek@intel.com> Reviewed-by: <sebastian.brzezinka@intel.com> Reviewed-by: Karol Latecki <karol.latecki@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.