Mirror test containers to public.cr.seqera.io to harden CI against quay.io outages#7195
Merged
Merged
Conversation
…ay.io outages The integration and validation test suites pull a handful of images from quay.io/nextflow/*. When quay.io is degraded these pulls fail (e.g. exit 125 on local Docker, MULTIQC failures on cloud backends) and the failures are unrelated to the code under test. Point the test configs at the same images mirrored to the Seqera public registry: quay.io/nextflow/<name>[:tag] -> public.cr.seqera.io/mirror/<name>[:tag] Updated references: - tests/nextflow.config, tests-v1/nextflow.config (tests) - validation/awsbatch.config, awsfargate.config, google.config (rnaseq-nf:latest) - validation/azure.config (rnaseq-nf:v1.1) - validation/awsbatch-unstage-fail.config (test-aws-unstage-fail:1.0) - validation/test-overwrite.nf (bash) Signed-off-by: Paolo Di Tommaso <[email protected]>
✅ Deploy Preview for nextflow-docs-staging canceled.
|
bentsherman
approved these changes
Jun 2, 2026
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
2 participants
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.
Rationale
The integration and validation test suites pull a handful of container images from
quay.io/nextflow/*. When quay.io is degraded, those pulls fail and the failures are unrelated to the code under test:tests/checks/*.nf) fail with exit 125 (container failed to start) — they pullquay.io/nextflow/tests;MULTIQCstep) — they pullquay.io/nextflow/rnaseq-nf.These exact symptoms were observed on recent CI runs (including on
master), caused by a quay.io outage rather than any regression.Change
Point the test configs at the same images, mirrored to the Seqera public registry:
The mirror images are byte-for-byte copies (identical digests, multi-arch preserved), so behaviour is unchanged — only the source registry differs.
Updated references
tests/nextflow.config,tests-v1/nextflow.configtestsvalidation/awsbatch.config,awsfargate.config,google.configrnaseq-nf:latestvalidation/azure.configrnaseq-nf:v1.1validation/awsbatch-unstage-fail.configtest-aws-unstage-fail:1.0validation/test-overwrite.nfbashAll five images have been mirrored and verified to resolve at
public.cr.seqera.io/mirror/with digests matching the quay.io sources.🤖 Generated with Claude Code