summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorScott Wittenburg <scott.wittenburg@kitware.com>2022-11-07 16:11:04 -0700
committerGitHub <noreply@github.com>2022-11-07 16:11:04 -0700
commitb3b675157c03a7c412d1d7f5b4696dc4d3a618a7 (patch)
tree4c8fb6bf694759f7ec5af83fe3f6fb319c1259f8
parent6241cdb27be0ed81a517f1601feac1b7e327170c (diff)
downloadspack-b3b675157c03a7c412d1d7f5b4696dc4d3a618a7.tar.gz
spack-b3b675157c03a7c412d1d7f5b4696dc4d3a618a7.tar.bz2
spack-b3b675157c03a7c412d1d7f5b4696dc4d3a618a7.tar.xz
spack-b3b675157c03a7c412d1d7f5b4696dc4d3a618a7.zip
gitlab ci: Add "script_failure" as a reason for retrying service jobs (#33420)
Somehow a network error when cloning the repo for ci gets categorized by gitlab as a script failure. To make sure we retry jobs that failed for that reason or a similar one, include "script_failure" as one of the reasons for retrying service jobs (which include "no specs to rebuild" jobs, update buildcache index jobs, and temp storage cleanup jobs.
-rw-r--r--lib/spack/spack/ci.py9
1 files changed, 8 insertions, 1 deletions
diff --git a/lib/spack/spack/ci.py b/lib/spack/spack/ci.py
index 56b3b249ac..aa54b71b3d 100644
--- a/lib/spack/spack/ci.py
+++ b/lib/spack/spack/ci.py
@@ -1167,7 +1167,14 @@ def generate_gitlab_ci_yaml(
"after_script",
]
- service_job_retries = {"max": 2, "when": ["runner_system_failure", "stuck_or_timeout_failure"]}
+ service_job_retries = {
+ "max": 2,
+ "when": [
+ "runner_system_failure",
+ "stuck_or_timeout_failure",
+ "script_failure",
+ ],
+ }
if job_id > 0:
if temp_storage_url_prefix: