ci: adjust the starting port range to runner concurrency stable
authorPierre-Yves David <pierre-yves.david@octobus.net>
Fri, 08 Nov 2024 21:22:02 +0100
branchstable
changeset 52213 63ad6b0c2b6a
parent 52212 d6ed4da850ea
child 52214 b3e696e879fc
ci: adjust the starting port range to runner concurrency If multiple job runs on the same runner, they should not use the port range.
contrib/heptapod-ci.yml
--- a/contrib/heptapod-ci.yml	Fri Nov 08 17:28:33 2024 +0100
+++ b/contrib/heptapod-ci.yml	Fri Nov 08 21:22:02 2024 +0100
@@ -105,6 +105,9 @@
         - echo "$FILTER"
         - echo "$FLAVOR"
         - echo "$WHEEL_TYPE"
+        - PORT_START=`expr 19051 + 1009 '*' $CI_CONCURRENT_ID`
+        - PORT_ARG="--port $PORT_START"
+        - echo $PORT_ARG
         - WHEEL_ARG=""
         - if test -n "$WHEEL_TYPE"; then
              PY_TAG=`$PYTHON -c 'import sys; v=sys.version_info; t=f"cp{v.major}{v.minor}"; print(f"{t}-{t}")'`;
@@ -122,6 +125,7 @@
         - HGTESTS_ALLOW_NETIO="$TEST_HGTESTS_ALLOW_NETIO"
           "$PYTHON" tests/run-tests.py
             --color=always
+            $PORT_ARG
             $WHEEL_ARG
             $FLAVOR
             $FILTER