changeset 53172:dbbf4d4ee720 stable

ci: always --retest error on Windows The Windows test are very flaky, let always re run failed test after the first run. This should help the overall flakiness making the windows test unreliable. This will make job with many legitimate failures slower to report their errors, but it helps the other cases so much that this is worse it.
author Pierre-Yves David <pierre-yves.david@octobus.net>
date Wed, 16 Apr 2025 22:54:12 +0200
parents 03c8d339aff2
children e667df349e5a 4682ca00a4f0
files contrib/heptapod-ci.yml
diffstat 1 files changed, 13 insertions(+), 0 deletions(-) [+]
line wrap: on
line diff
--- a/contrib/heptapod-ci.yml	Wed Apr 16 22:51:06 2025 +0200
+++ b/contrib/heptapod-ci.yml	Wed Apr 16 22:54:12 2025 +0200
@@ -518,6 +518,8 @@
         # it for now
         - C:/hgdev/MinGW/msys/1.0/bin/sh.exe -c 'cd "$OLDPWD" && echo tests/test-clonebundles-autogen.t > $TMP_WORK_DIR/windows-skip.txt'
 
+        # we immediately run with --retest in case of error as the windows test
+        # are so flaky.
         - C:/hgdev/MinGW/msys/1.0/bin/sh.exe
           --login -c 'cd "$OLDPWD"
             && HGTESTS_ALLOW_NETIO="$TEST_HGTESTS_ALLOW_NETIO"
@@ -529,6 +531,17 @@
                --port `expr 19051 + 1009 "*" $CI_CONCURRENT_ID`
                --shard-index $CI_NODE_INDEX --shard-total $CI_NODE_TOTAL
                $FILTER
+               $RUNTEST_ARGS
+            || HGTESTS_ALLOW_NETIO="$TEST_HGTESTS_ALLOW_NETIO"
+               $PYTHON tests/run-tests.py
+               --retest
+               --color=always
+               --tail-report
+               $WHEEL_ARG
+               $FLAVOR
+               --port `expr 19051 + 1009 "*" $CI_CONCURRENT_ID`
+               --shard-index $CI_NODE_INDEX --shard-total $CI_NODE_TOTAL
+               $FILTER
                $RUNTEST_ARGS;
           '
     variables: