From: Michal Nowak Date: Wed, 25 Mar 2026 12:31:49 +0000 (+0100) Subject: Set RUNNER_SCRIPT_TIMEOUTs X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=40448cb421cc6d65c6ba14ee4b764dd3ec05475f;p=thirdparty%2Fbind9.git Set RUNNER_SCRIPT_TIMEOUTs Sometimes jobs can get stuck and be terminated by GitLab, leaving us without artefacts that could contain useful information about why the job got stuck. Assisted-by: Claude:claude-opus-4-7 (cherry picked from commit e3d2f5ad948f977df67a349601bd4743f6777539) --- diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index fb1f3ec0dae..b55d3e85177 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -1,4 +1,7 @@ variables: + # The default timeout is 60 minutes. Set RUNNER_SCRIPT_TIMEOUT to 55m to + # leave room for the after_script timeout that defaults to 5m. + RUNNER_SCRIPT_TIMEOUT: 55m # Not normally needed, but may be if some script uses `apt-get install`. DEBIAN_FRONTEND: noninteractive # Locale settings do not affect the build, but might affect tests. @@ -535,6 +538,9 @@ stages: SHOTGUN_ROUNDS: 5 when: manual allow_failure: true + timeout: 2h + variables: + RUNNER_SCRIPT_TIMEOUT: 1h55m script: - if [ -n "$WEEKDAY" ] && [ "$(date +%w)" != "$WEEKDAY" ]; then exit 0; fi # if WEEKDAY is set, only run on those days - if [ -z "$BASELINE" ]; then export BASELINE=$BIND_BASELINE_VERSION; fi # this dotenv variable can't be set in the rules section, because rules are evaluated before any jobs run @@ -563,7 +569,6 @@ stages: needs: - job: ci-variables artifacts: true - timeout: 2h .system_test_common: &system_test_job <<: *default_triggering_rules