Commit 9c659fb1 authored Jan 16, 2020 by Seth Howell Committed by Tomasz Zawadzki Jan 20, 2020

test/fuzz fix end of test behavior.



The fuzz jobs should fail if the nvmf or vhost target crashed while they
were running. Otherwise they should pass. Some recent changes to the
way killprocess and nvmftestfini work were causing this to break. This
change fixes that.

Change-Id: Id14fd47c2d8c7d91358c5e8a69e53ec4cf33ddce
Signed-off-by: Seth Howell <seth.howell@intel.com>
Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/481911


Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
Reviewed-by: Jim Harris <james.r.harris@intel.com>
Community-CI: SPDK CI Jenkins <sys_sgci@intel.com>

parent 20c5fc9d

test/fuzz/autofuzz_nvmf.sh

+0 −2

Original line number	Diff line number	Diff line
		@@ -47,7 +47,5 @@ $rpc_py nvmf_delete_subsystem nqn.2016-06.io.spdk:cnode1
		trap - SIGINT SIGTERM EXIT

		nvmfcleanup
		killprocess $nvmfpid

		nvmftestfini
		timing_exit nvmf_fuzz_test

test/fuzz/autofuzz_vhost.sh

+0 −4

Original line number	Diff line number	Diff line
		@@ -70,9 +70,5 @@ $fuzz_generic_rpc_py framework_start_init
		wait $fuzzpid

		trap - SIGINT SIGTERM exit
		set +e
		killprocess $vhostpid
		echo $?
		set -e
		killprocess $fuzzpid
		timing_exit vhost_fuzz_test