The reconnect timeout test case expects a socket READ error to trigger the reconnect poller in bdev_nvme module, but we use the `verify` IO workload to send IO requests which may cause the client doesn't receive any error, because it will send WRITE commands first. Fix issue #2595. Change-Id: Ibc6b534d157552cdb2b55a03c869e254ec4c462e Signed-off-by: Changpeng Liu <changpeng.liu@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/13840 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Dong Yi <dongx.yi@intel.com> Reviewed-by: Michal Berger <michal.berger@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@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.