Spdk/test/nvmf
Jim Harris 713333fdc9 test/nvmf: add some delays in discovery.sh
The test script does sequences like the following:

1) Add a host to an existing subsystem on target A
2) Check application B to see if it has received a
   discovery AEN and attached to that subsystem

But we have to account for some delay between 1 and 2.
Application B has to receive the discovery AEN, get
the discovery log page, parse the new log page entry
and then connect to the NVM subsystem.

Fixes issue #2420.

Signed-off-by: Jim Harris <james.r.harris@intel.com>
Change-Id: I160ed117ccd92bfb848f0075494a0d516b341191
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/11934
Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com>
Reviewed-by: Changpeng Liu <changpeng.liu@intel.com>
Reviewed-by: Shuhei Matsumoto <smatsumoto@nvidia.com>
Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2022-03-14 08:44:21 +00:00
..
host test/nvmf: add some delays in discovery.sh 2022-03-14 08:44:21 +00:00
target test: add explicit listener for discovery subsystem 2022-02-28 11:06:16 +00:00
common.sh test/nvmf: Use device name instead of driver's 2022-03-01 16:01:37 +00:00
nvmf.sh test/nvmf: Rename the current script as failover 2022-01-17 14:25:15 +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.