Skip to content

.gitlab-ci.yml: retry if conda build fails due to corrupted package cache

Karl Wette requested to merge ANU-CGA/lalsuite:conda-build-corrupted-cache into master

Description

Conda jobs sometimes fail with errors like:

failed to create env, retrying.  exception was: The package for ld_impl_linux-64 located at /builds/ANU-CGA/lalsuite/.cache/conda/pkgs/ld_impl_linux-64-2.40-h41732ed_0
appears to be corrupted. The path 'bin/x86_64-conda-linux-gnu-ld'
...

(There are usually many of these messages which then overflow the CI job log.) This MR catches these errors, deletes the .cache/conda/pkgs directory, and tries again, which should then succeed (or at least not fail with corruption errors).

Example job log where this failure occurs, but is recovered with this MR: https://git.ligo.org/ANU-CGA/lalsuite/-/jobs/2719252/raw (search for failed to create env).

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

If any of the Backwards Incompatible check boxes are ticked please provide a justification why this change is necessary and why it needs to be done in a backwards incompatible way.

Review Status

cc @duncanmmacleod @adam-mercer

Merge request reports