Commit 29e5c544 authored by Shuhei Matsumoto's avatar Shuhei Matsumoto Committed by Tomasz Zawadzki
Browse files

test/nvmf: Leave 2 seconds before starting the next shutdown test case 



On the target side, disconnection process is asynchronous and ack is
sent to the initiator before completion.  This has caused latent
failure in a test case.  As a workaround, leave 2 seconds before
starting to the next test case for now.  Better solution will be
followed and so we don't care much about the location to insert
sleep.

Signed-off-by: default avatarShuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>
Change-Id: Id49349e3b7303ef9523b73d7a04d4e9837246c44
Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/479102


Tested-by: default avatarSPDK CI Jenkins <sys_sgci@intel.com>
Community-CI: SPDK CI Jenkins <sys_sgci@intel.com>
Community-CI: Broadcom SPDK FC-NVMe CI <spdk-ci.pdl@broadcom.com>
Reviewed-by: default avatarChangpeng Liu <changpeng.liu@intel.com>
Reviewed-by: default avatarJim Harris <james.r.harris@intel.com>
parent f594537a

test/nvmf/target/shutdown.sh

+5 −0
Original line number Diff line number Diff line
@@ -52,6 +52,11 @@ function nvmf_shutdown_tc1 { 


	# Connect with bdevperf and confirm it works

	$rootdir/test/bdev/bdevperf/bdevperf -r /var/tmp/bdevperf.sock -c $testdir/bdevperf.conf -q 64 -o 65536 -w verify -t 1



	# We have seen the latent failure that the test 2 will see that the target is still finishing

	# tearing down the qpair when connecting it.  As a workaround, leave a few seconds here to wait

	# for the completion.

	sleep 2

}



# Test 2: Kill initiator unexpectedly with I/O outstanding