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> |
||
---|---|---|
.. | ||
aer.sh | ||
async_init.sh | ||
bdevperf.sh | ||
discovery.sh | ||
dma.sh | ||
failover.sh | ||
fio.sh | ||
identify_kernel_nvmf.sh | ||
identify.sh | ||
multicontroller.sh | ||
multipath.sh | ||
perf.sh | ||
target_disconnect.sh | ||
timeout.sh |