autotest: Don't run spdk_dd tests under crypto job
Currently, crypto job also executes tests from the SPDK_TEST_BLOCKDEV suite, including spdk_dd tests. The dd tests under a bare-metal system can take up to 4 minutes alone and that brings the crypto job to the very edge of timing out. Since these tests are extensively covered under separate vg jobs we won't lose any coverage by excluding them from crypto's - the basic set of SPDK_TEST_BLOCKDEV tests would still remain as part of this job. Fixes: #2017 Signed-off-by: Michal Berger <michalx.berger@intel.com> Change-Id: I877e63de1e43aeb06c134fdacd6f5efbbe2a6317 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/8545 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Pawel Piatek <pawelx.piatek@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Krzysztof Karas <krzysztof.karas@intel.com>
This commit is contained in:
parent
a82e8478ea
commit
c6db5f41e5
@ -190,7 +190,14 @@ if [ $SPDK_RUN_FUNCTIONAL_TEST -eq 1 ]; then
|
||||
|
||||
if [[ $(uname -s) == Linux ]]; then
|
||||
if [[ $SPDK_TEST_BLOCKDEV -eq 1 || $SPDK_TEST_URING -eq 1 ]]; then
|
||||
run_test "spdk_dd" test/dd/dd.sh
|
||||
# The crypto job also includes the SPDK_TEST_BLOCKDEV in its configuration hence the
|
||||
# dd tests are executed there as well. However, these tests can take a significant
|
||||
# amount of time to complete (up to 4min) on a physical system leading to a potential
|
||||
# job timeout. Avoid that by skipping these tests - this should not affect the coverage
|
||||
# since dd tests are still run as part of the vg jobs.
|
||||
if [[ $SPDK_TEST_CRYPTO -eq 0 ]]; then
|
||||
run_test "spdk_dd" test/dd/dd.sh
|
||||
fi
|
||||
fi
|
||||
fi
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user