Shuhei Matsumoto f594537a48 bdevperf: Reset g_run_rc to 0 after sending RPC reply ... When RPC kicks the test and the test results in error, RPC response should return error but bdevperf application should not return error. RPC can kick the test multiple times, and if RPC kicks the test again and it completes normally, RPC response should return success. So reset g_run_rc to 0 after sending RPC response. Signed-off-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Change-Id: I59a7c06a293ba7f7b5caa8171bcfb54d736524da Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/479914 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>		2020-01-16 09:16:52 +00:00
..
.gitignore	test: move the bdev directory up one level	2018-03-23 19:45:09 -04:00
bdevperf.c	bdevperf: Reset g_run_rc to 0 after sending RPC reply	2020-01-16 09:16:52 +00:00
bdevperf.py	bdevperf: do not start tests until RPC is sent	2019-07-10 05:11:25 +00:00
Makefile	lib: move trace_rpc into lib/trace	2019-08-19 06:10:30 +00:00