34ae11720d
The shell_Restore_x variable and xtrace_restore were attempting to accomplish the exact same thing. However, when assigning shell_restore_x, if -x was not set, then the assignment would result in an error causing the scripts to fail. So just get rid of that variable entirely and replace it with the more robust xtrace_disable, xtrace_restore mechanism. Change-Id: Ic823ad8433bd3dc181aaa0930297cd9d74bcf528 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/477966 Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: SPDK CI Jenkins <sys_sgci@intel.com> |
||
---|---|---|
.. | ||
aer | ||
deallocated_value | ||
e2edp | ||
err_injection | ||
overhead | ||
perf | ||
reset | ||
sgl | ||
startup | ||
hotplug.sh | ||
hw_hotplug.sh | ||
Makefile | ||
nvme_opal.sh | ||
nvme.sh | ||
spdk_nvme_cli_cuse.sh | ||
spdk_nvme_cli.sh | ||
spdk_smartctl_cuse.sh |