Repository navigation
ci: run nightly GPU regression tests - #148
Merged
Merged
Conversation
Signed-off-by: Farhad Ramezanghorbani <farhadr@nvidia.com>
Contributor
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the
|
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
Run the full GPU regression workflow daily at 09:23 UTC, including when there are no new commits. The existing workflow builds the CI image and runs pytest plus the two-GPU context-parallel tests. Scheduled runs now fail if fewer than two GPUs are visible, and use a separate concurrency group so they cannot replace pending push or manual runs.
Test plan
No new permanent tests are needed for this workflow-only change. No public Python symbols or documentation APIs changed.
Activation
The nightly schedule becomes active after merge into main. Existing hourly runner heartbeat and watchdog workflows remain in place. GitHub can disable public-repository schedules after 60 days without repository activity; scheduled execution is not a guaranteed resource-retention mechanism.
Review
Codeowner approval is required by the repository ruleset.