Since both stdout and stderr of the db_bench run is redirected to a file, xtrace won't write out anything of value in case said run fails. Example: https://ci.spdk.io/public_build/autotest-per-patch_4071.html To avoid looking into the file directly, try to locate last .txt that was written out and dump its contents to stderr to increase the visibility of what might have caused the failure. Change-Id: Ic4873626e979130f2722a4f2d5266d93bc2bde76 Signed-off-by: Michal Berger <michalx.berger@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/959 Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> |
||
---|---|---|
.. | ||
fuse | ||
mkfs | ||
rocksdb | ||
blobfs.sh | ||
Makefile |