Skip to content

Fix CI container name collision for parallel matrix jobs#15

Draft
sunway513 wants to merge 4 commits intomainfrom
fix/ci-unique-container-names
Draft

Fix CI container name collision for parallel matrix jobs#15
sunway513 wants to merge 4 commits intomainfrom
fix/ci-unique-container-names

Conversation

@sunway513
Copy link
Owner

Summary

  • Fix CI container name collision for parallel matrix jobs
  • Quote CONTAINER_NAME variable for shell safety

Mirror of upstream draft ROCm#212.

sunway513 and others added 4 commits February 12, 2026 23:41
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.
@sunway513 sunway513 marked this pull request as draft February 21, 2026 23:09
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.

2 participants