Spdk/test/nvmf
Maciej Wawryk 53147e0dc8 test: fix issue with changing device names in waitforblk function
During test before upgrading our vm's to Fedora31 there were issue with failing
nvmf test on function waitforblk. In some cases hardcoded nvme0n1 name was not
found in system. Here is fix that change searching by name to searching by nvme
serial.

Signed-off-by: Maciej Wawryk <maciejx.wawryk@intel.com>
Change-Id: Ic5ee70804652a057fa26b8cc004b5227262d2122
Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/478471
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Jim Harris <james.r.harris@intel.com>
Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
Reviewed-by: Seth Howell <seth.howell@intel.com>
Community-CI: SPDK CI Jenkins <sys_sgci@intel.com>
2020-01-20 10:00:06 +00:00
..
host test: eliminate case and suite from run_test 2019-12-24 08:24:42 +00:00
target test: fix issue with changing device names in waitforblk function 2020-01-20 10:00:06 +00:00
common.sh test: fix issue with changing device names in waitforblk function 2020-01-20 10:00:06 +00:00
nvmf.sh test: move report_test_completion into run_test 2020-01-14 07:49:08 +00: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.