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> |
||
---|---|---|
.. | ||
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.