Skip to content

ci: retry registry download flakes, cache the VM tests' images - #57

Merged
thatbagu merged 2 commits into
mainfrom
fix/ci-image-cache
Nov 20, 2026
Merged

thatbagu merged 2 commits into
mainfrom
fix/ci-image-cache

Conversation

@thatbagu

@thatbagu thatbagu commented Nov 20, 2026 •

Copy link
Copy Markdown
Owner

The VM tests' container images come from registries that time out now and then. ecr-public's redis failed several PR runs in a row (#53's vm-cluster today). And the per-job store cache, capped at 3 GB, doesn't keep these images.

  • Build checks now retries any fatal error from an image download (ecr-public manifest timeouts, quay.io mid-blob EOFs) the way it already retried GitHub's 5xx on chart downloads: up to 3 attempts. Real failures fail on the last attempt.
  • Image tarballs go to the binary cache (*-docker-image-*.tar) along with the charts, so later runs substitute them instead of hitting the registry. Still only where CACHIX_AUTH_TOKEN is set.

🤖 Generated with Claude Code

thatbagu and others added 2 commits November 20, 2026 21:42
The VM tests' container images come from registries that time out now and
then (ecr-public's redis failed several PR runs in a row), and the
per-job store cache (3 GB) doesn't keep them. The build now retries on
registry failures as it does on GitHub's, and image downloads go to the
binary cache with the charts.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
quay.io failed mid-blob (unexpected EOF), which the registry patterns
didn't cover. Any fatal error from an image fetch is retried now.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@thatbagu
thatbagu merged commit 16d857f into main Nov 20, 2026
21 checks passed
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