ci: make buildcache index update non-fatal#921
Open
wdconinc wants to merge 2 commits into
Open
Conversation
The 'spack buildcache update-index' step can fail with transient errors such as '503: Egress is over the account limit.' which are unrelated to the actual build result. Add continue-on-error: true to both 'Update buildcache index' steps so these infrastructure hiccups do not mark an otherwise successful build as failed. Co-authored-by: Copilot <[email protected]>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR makes the buildcache index update step non-fatal in CI so transient registry/buildcache failures do not fail otherwise successful builds.
Changes:
- Adds
continue-on-error: trueto theUpdate buildcache indexstep in the environment build job. - Adds
continue-on-error: trueto the equivalent step in the changed-package build job.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
spack buildcache update-indexstep can fail with transient errors such as503: Egress is over the account limit.which are unrelated to the actual build result. Addcontinue-on-error: trueto both Update buildcache index steps (in thebuild-environmentandbuild-packagesjobs) so these infrastructure hiccups do not mark an otherwise successful build as failed.Fixes the failure seen at https://github.com/eic/eic-spack/actions/runs/25825838204/job/75878671152?pr=917#step:15:94