gitlab-ci: Do not retry for job_execution_timeout
authorAndrew Bartlett <abartlet@samba.org>
Thu, 14 Oct 2021 07:24:49 +0000 (20:24 +1300)
committerAndrew Bartlett <abartlet@samba.org>
Fri, 15 Oct 2021 09:09:36 +0000 (09:09 +0000)
If we timeout, we should just stop at 2 hours, not waste 6 hours (3 x 2 hours).

This is for when the job runs long for any reason, currently the
reasons for a timeout are not transient, we need to either change
the timeout or fix the system.  Likewise if the tests get into a loop
or deadlock we want to see that as a failure.

BUG: https://bugzilla.samba.org/show_bug.cgi?id=14863

Signed-off-by: Andrew Bartlett <abartlet@samba.org>
Reviewed-by: Douglas Bagnall <douglas.bagnall@catalyst.net.nz>
.gitlab-ci-main.yml

index d876923f9e78b0d894f893f11749a1a2c2f5e897..6cf2a2de3398de9ce68288c4642c799794c04f53 100644 (file)
@@ -148,7 +148,6 @@ include:
       - api_failure
       - runner_unsupported
       - stale_schedule
-      - job_execution_timeout
       - archived_failure
       - scheduler_failure
       - data_integrity_failure