Fix CI container name collision for parallel matrix jobs#15
Draft
Fix CI container name collision for parallel matrix jobs#15
Conversation
Multiple matrix jobs on the same runner used a hardcoded container name
"atom_test", causing cleanup steps to kill sibling jobs' containers.
Use CONTAINER_NAME=atom_test_${strategy.job-index} so each job operates
on its own container without interference.
GPU isolation is already handled by gha-render-devices, so the container
name collision was the sole root cause of the intermittent GPU OOM errors.
Address review suggestion: quote all $CONTAINER_NAME references in docker commands for defensive shell hygiene.
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
Mirror of upstream draft ROCm#212.