Repository navigation
[ci] Preserve GPU access and isolate container scratch files - #6512
Merged
Merged
Conversation
richardoo-707
marked this pull request as ready for review
November 5, 2026 00:55
yuxuan-lou
approved these changes
Nov 5, 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
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.
Fixes #6509. Related to the Layer 2 infrastructure failures on #6506.
GPU containers could lose device permissions after a cgroup/resource update while
/dev/nvidia*remained visible. Resolve allocated UUIDs to actual device minors from NVIDIA's XML inventory and explicitly register those GPU nodes and the CUDA control nodes with Docker. Every visible GPU must then complete an allocation, computation and synchronization probe before tests.Move disposable source, HOME and compiler caches to a private
/tmptmpfs to avoid the observed overlay2 removal failure. Record the container exit code and cleanup error separately; cleanup failures still fail the job and preserve the original execution exception.Numerical acceptance requires real Git provenance. Fetch the pinned commit/tree metadata, reconstruct file objects from the compressed archive, and verify the complete Git tree with lazy downloads disabled. The standalone
.gitsurvives the container's private source copy and supports offline commit and dirty-tree checks.Validation on head
9382593b42c5ab0e70ccb8e1147a45b554ced74a, tested merge05978230a94352c85ad45e67790851188c033687:All three GPU containers exited 0 and were removed successfully. Runtime: H20-5, Python 3.10.12 / Torch 2.13.0+cu130, existing approved image
sha256:ae8ff34bf340a692803edca6e0f38a576fc1a2b206c01b4ef6f7c2a40dfd8c10. Regular Layer 2 usesFAST_MODE=1/FAST_TEST=1; this final run needed no test reruns. The earlier Draft smoke also passed 22 batch-4a tests with fast mode disabled.A controlled two-H20 probe on runtime-fix commit
d31489ff134e99c9dcd267e1508b426f7d686d1ealso computed successfully before and after updating only its own container's CPU quota. Source checkout regressions cover offline copied metadata, gitlinks, a missing SHA and a mismatched archive. Repository pre-commit and runner-policy checks passed.The dependency image, GPU pool, test selection, numerical tolerances and
version.txtare unchanged. tmpfs shares the existing container memory limit, capped atCOLOSSAL_CI_MEMORY. Existing Docker records already stuck in removal still require administrator maintenance. Four/eight-GPU Layer 3 is outside this validation.