Spdk/test/nvmf
Seth Howell 87dea05be4 test/nvmf: call nvmftestinit before checking IP.
The first IP is not configured until after nvmftestinit.

Change-Id: Icfc4ce40e357d36da2c50fefb3b967806966eb80
Signed-off-by: Seth Howell <seth.howell@intel.com>
Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/476648
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>
Reviewed-by: Maciej Wawryk <maciejx.wawryk@intel.com>
Reviewed-by: Jim Harris <james.r.harris@intel.com>
Community-CI: Broadcom SPDK FC-NVMe CI <spdk-ci.pdl@broadcom.com>
2019-12-05 12:37:23 +00:00
..
host test/nvmf: call nvmftestinit before checking IP. 2019-12-05 12:37:23 +00:00
target test: Shellcheck - correct rule: Consider using { cmd1; cmd2; } 2019-11-22 13:51:15 +00:00
common.sh test/nvmf: call killprocess only when nvmfpid exists 2019-12-05 12:37:23 +00:00
nvmf.sh test: Shellcheck - correct rule: Expanding an array 2019-11-27 07:08:57 +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.