ivampiresp/Spdk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

test/fuzz fix end of test behavior.

Browse Source 
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>
This commit is contained in:
Seth Howell 2020-01-16 17:02:36 -07:00 committed by Tomasz Zawadzki
parent 20c5fc9dce
commit 9c659fb125
2 changed files with 0 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
test/fuzz/autofuzz_nvmf.sh
View File

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

4
test/fuzz/autofuzz_vhost.sh
View File

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