226a705d83
Running create/delete loop 50 times causes the test to take over 10 minutes and time out in nightly version. We have various code analyzer tests in place so running the same script block over 50 times in hope of detecting memory leak or some similar defect seems a bit redundant. Signed-off-by: Karol Latecki <karol.latecki@intel.com> Change-Id: Icb2acb0ffbbe63d3004532d0b4a261152891216a Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/9166 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Reviewed-by: Maciej Wawryk <maciejx.wawryk@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Pawel Piatek <pawelx.piatek@intel.com> Reviewed-by: Jim Harris <james.r.harris@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.