ci: retry NVHPC image pull on transient nvcr.io timeouts#1554
Merged
Conversation
The bare 'docker pull' in the NVHPC jobs fails the whole job when nvcr.io returns 'context deadline exceeded', which happens sporadically with ~30 matrix jobs pulling concurrently. Retry up to 5 times with linear backoff; pulls resume completed layers so retries are cheap.
|
Claude Code Review Head SHA: c8995c4 Files changed:
Findings:
|
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.
Problem
NVHPC matrix jobs sporadically fail at the Pull NVHPC container step with:
Example: NVHPC 25.7 (cpu) in run 27312594672, where 1 of 30 NVHPC jobs hit the timeout while the other 29 pulled the same registry fine — a transient nvcr.io flake, likely aggravated by ~30 concurrent pulls per run.
Fix
Retry
docker pullup to 5 times with linear backoff (30s, 60s, ...). Docker resumes already-downloaded layers, so retries are cheap. Worst case adds ~5 min before failing with an explicit error annotation.