test/nvmf: Manually remove cpu lock files
Signed-off-by: Michal Berger <michal.berger@intel.com> Change-Id: Idcace2a8f7d47b9d508089b8171f1121fd819c82 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/15905 Reviewed-by: Pawel Piatek <pawelx.piatek@intel.com> Reviewed-by: Konrad Sztyber <konrad.sztyber@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
This commit is contained in:
parent
4f857ce593
commit
d0e6ba0a3c
@ -90,6 +90,12 @@ function nvmf_host_management() {
|
||||
# and so it will never shut down. Just kill it.
|
||||
kill -9 $perfpid || true
|
||||
|
||||
# Since we abruptly terminate $perfpid above, we need to do some cleanup on our own.
|
||||
# In particular, we need to get rid of the cpu lock files that may potentially prevent
|
||||
# the next instance of bdevperf from running.
|
||||
# FIXME: Can't we just SIGTERM $perfpid above?
|
||||
rm -f /var/tmp/spdk_cpu_lock*
|
||||
|
||||
# Run bdevperf
|
||||
$rootdir/build/examples/bdevperf -r /var/tmp/bdevperf.sock --json <(gen_nvmf_target_json "0") -q 64 -o 65536 -w verify -t 1
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user