Skip to content

ci: a cache export error should not fail the image publish - #1435

Open
splitsec2 wants to merge 1 commit into
calibrain:mainfrom
splitsec2:ci/cache-export-not-fatal
Open

splitsec2 wants to merge 1 commit into
calibrain:mainfrom
splitsec2:ci/cache-export-not-fatal

Conversation

@splitsec2

@splitsec2 splitsec2 commented Oct 4, 2026 •

Copy link
Copy Markdown
Contributor

Kept small on purpose so it's easy to review. Same kind of small fix as #1429 to #1432, so see the question in #1429 about separate PRs versus combined. I'm sending them separately until I hear otherwise.

cache-to: type=gha has no ignore-error, and the Docker docs list it as defaulting to false. If the GitHub Actions cache service errors while exporting, the build step fails after the image has been built and pushed, so the attestation step is skipped. The docs suggest ignore-error=true when cache export is optional, which it is here.

I haven't seen an export fail on this repo, so this is a precaution and I can't reproduce it locally. It's a one-line change plus a comment.

The one red check is the existing clock-dependent test test_a_queued_torrent_asks_for_a_grace_once, which fails on any runner that booted recently. It is fixed in #1426 and is not caused by this change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant