Skip to content

CI: go back to retry running jobs on some failure types

Karl Wette requested to merge ANU-CGA/lalsuite:ci-retry into master

Description

In !2000 (merged) I went back to using retry: 0 for most CI jobs, so prevent jobs being unnecessarily re-run when the failure is a bug in the code. However, the CI should still re-run jobs that fail due to GitLab system failures, so that the user doesn't have to manually so that.

With this MR the CI should re-run jobs on most GitLab system failures. It excludes script failures (which are likely to be a broken job) or timeout failures (which could indicate jobs needs a longer timeout, or at least should be examined why it timed out).

API Changes and Justification

Backwards Compatible Changes

  • This change does not modify any class/function/struct/type definitions in a public C header file or any Python class/function definitions
  • This change adds new classes/functions/structs/types to a public C header file or Python module

Backwards Incompatible Changes

  • This change modifies an existing class/function/struct/type definition in a public C header file or Python module
  • This change removes an existing class/function/struct/type from a public C header file or Python module

Review Status

cc @adam-mercer

Merge request reports