Skip to content

Revert "CI: do not retry jobs by default"

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

Description

In !2000 (merged) I changed the CI so that not all jobs were retried by default. Since then I've seen more random failures in jobs (as might have been expected). Unfortunately it looks like not all system failures are covered in the retry categories listed before; e.g. if some runners fails during the job (something to do with "pods"??) they register as a script error and are not retried.

Since it appears we can't reliably distinguish runner failures from actual build failures, it's probably going to be less tedious to retry all jobs at least once to guard against the former.

With the MR all jobs will be tried at least one, except for jobs which extend .deploy and .koji:build.

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