Repository navigation
ci: Don't fail builds when saving the cache fails - #21
Merged
Merged
Conversation
The first main build after #20 failed on pg-18 (arm64) with a 504 from the GitHub Actions cache while exporting a layer. The image had built and passed its tests; only the cache write failed. With ignore-error a cache outage only costs time on the next build. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QTN7At86i5TYDmozENSNv8
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.
Summary
The first
mainbuild after #20 failed onpg-18 (arm64)with a504from the GitHub Actions cache while exporting a layer (error writing layer blob). The build had otherwise succeeded. Because a job failed, nothing was published, which is correct, but it took a manual re-run.This adds
ignore-error=truetocache-to. If the cache backend is down, the build still succeeds; the only cost is that the next build is slower. Cache reads are unaffected.Testing
actionlint passes. This PR's CI runs with the change.
🤖 Generated with Claude Code
https://claude.ai/code/session_01QTN7At86i5TYDmozENSNv8