If we want to catch new failures faster we have a better chance if CI doesn't auto-retry (once).
Signed-off-by: Dumitru Ceara <[email protected]> --- NOTE: Sending this as RFC to start the discussion with the community. --- .ci/linux-build.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.ci/linux-build.sh b/.ci/linux-build.sh index 907a0dc6c9..64f7a96d91 100755 --- a/.ci/linux-build.sh +++ b/.ci/linux-build.sh @@ -66,7 +66,7 @@ function execute_tests() export DISTCHECK_CONFIGURE_FLAGS="$OPTS" if ! make distcheck CFLAGS="${COMMON_CFLAGS} ${OVN_CFLAGS}" $JOBS \ - TESTSUITEFLAGS="$JOBS $TEST_RANGE" RECHECK=yes + TESTSUITEFLAGS="$JOBS $TEST_RANGE" then # testsuite.log is necessary for debugging. cat */_build/sub/tests/testsuite.log @@ -81,7 +81,7 @@ function execute_system_tests() configure_ovn $OPTS make $JOBS || { cat config.log; exit 1; } - if ! sudo make $JOBS $type TESTSUITEFLAGS="$TEST_RANGE" RECHECK=yes; then + if ! sudo make $JOBS $type TESTSUITEFLAGS="$TEST_RANGE"; then # $log_file is necessary for debugging. cat tests/$log_file exit 1 -- 2.31.1 _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
