Spdk/test/nvmf
Michal Berger f2c7c28b2b test/nvmf: Nuke all SPDK net namespaces before starting tests
This is to make sure we won't lose any net interfaces needed for the
phy tests in case they got stuck behind lingering namespace.

Signed-off-by: Michal Berger <michalx.berger@intel.com>
Change-Id: Ic83bc5cca8b536bb3e72fbceb31d2560d840d05e
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/9795
Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Jim Harris <james.r.harris@intel.com>
Reviewed-by: wanghailiang <hailiangx.e.wang@intel.com>
Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2022-06-30 13:32:26 -04:00
..
host bdev/nvme: Don't allow a second identical path for failover 2022-06-30 13:32:26 -04:00
target test: use single core when testing nvme fuzz with nvmf target 2022-06-30 13:32:25 -04:00
common.sh test/nvmf: Nuke all SPDK net namespaces before starting tests 2022-06-30 13:32:26 -04:00
nvmf.sh test/vfio-user: enable NVMe compliance tests with vfio-user 2022-06-30 13:32:26 -04:00
README.md test: add parse_common_script_args function 2019-05-22 23:43:51 +00:00

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.