Making separate integration test for nccl test in gke a3 ultra#4622
Merged
shubpal07 merged 2 commits intoSep 8, 2025
Merged
Conversation
Contributor
Author
|
Tested to new build file for creating new trigger named |
kadupoornima
reviewed
Sep 8, 2025
kadupoornima
approved these changes
Sep 8, 2025
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.
This PR refactors the monolithic gke-a3-ultragpu integration test into two distinct, focused tests: a lightweight Kueue validation test and a heavyweight NCCL performance test.
This change is critical to address a series of severe stability issues discovered during the Kueue-on-Helm migration. The previous, single-test structure was found to be brittle and was the root cause of CI failures where the cluster would self-destruct by scaling its own GPU nodes to zero. This new structure is more stable, provides faster feedback, is more resource-efficient, and completely avoids this failure.
Submission Checklist
NOTE: Community submissions can take up to 2 weeks to be reviewed.
Please take the following actions before submitting this pull request.