test/rocksdb: run blobcli -D after test is complete

We especially want to do this when a test fails, but
running it in passing cases too ensures spdk_bs_dump at
least gets run on every patch through the test pool.

Signed-off-by: Jim Harris <james.r.harris@intel.com>
Change-Id: I2d696dbf21d14681a73cb990933cba4e57a5f8a5

Reviewed-on: https://review.gerrithub.io/414482
Tested-by: SPDK Automated Test System <sys_sgsw@intel.com>
Reviewed-by: Daniel Verkamp <daniel.verkamp@intel.com>
Reviewed-by: Ben Walker <benjamin.walker@intel.com>
This commit is contained in:
Jim Harris 2018-06-08 08:13:35 -07:00
parent d1d22046df
commit 5f0c61a589

View File

@ -17,6 +17,10 @@ run_step() {
echo done. echo done.
} }
run_bsdump() {
$rootdir/examples/blob/cli/blobcli -c $ROCKSDB_CONF -b Nvme0n1 -D &> bsdump.txt
}
testdir=$(readlink -f $(dirname $0)) testdir=$(readlink -f $(dirname $0))
rootdir=$(readlink -f $testdir/../../..) rootdir=$(readlink -f $testdir/../../..)
source $rootdir/test/common/autotest_common.sh source $rootdir/test/common/autotest_common.sh
@ -44,7 +48,7 @@ timing_exit db_bench_build
cp $rootdir/etc/spdk/rocksdb.conf.in $ROCKSDB_CONF cp $rootdir/etc/spdk/rocksdb.conf.in $ROCKSDB_CONF
$rootdir/scripts/gen_nvme.sh >> $ROCKSDB_CONF $rootdir/scripts/gen_nvme.sh >> $ROCKSDB_CONF
trap 'rm -f $ROCKSDB_CONF; exit 1' SIGINT SIGTERM EXIT trap 'run_bsdump; rm -f $ROCKSDB_CONF; exit 1' SIGINT SIGTERM EXIT
timing_enter mkfs timing_enter mkfs
$rootdir/test/blobfs/mkfs/mkfs $ROCKSDB_CONF Nvme0n1 $rootdir/test/blobfs/mkfs/mkfs $ROCKSDB_CONF Nvme0n1
@ -124,6 +128,7 @@ timing_exit rocksdb_randread
trap - SIGINT SIGTERM EXIT trap - SIGINT SIGTERM EXIT
run_bsdump
rm -f $ROCKSDB_CONF rm -f $ROCKSDB_CONF
report_test_completion "blobfs" report_test_completion "blobfs"