Skip to content

[c10d] Test multiple CUDA Graph captures#150040

Closed
kwen2501 wants to merge 1 commit intogh/kwen2501/136/basefrom
gh/kwen2501/136/head
Closed

[c10d] Test multiple CUDA Graph captures#150040
kwen2501 wants to merge 1 commit intogh/kwen2501/136/basefrom
gh/kwen2501/136/head

Conversation

@kwen2501
Copy link
Collaborator

@kwen2501 kwen2501 commented Mar 26, 2025 •
edited
Loading

Stack from ghstack (oldest at bottom):

  1. Do multiple captures
  2. Perform multiple collectives in one capture
  3. Multiple replays (existing)

cc @H-Huang @awgu @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @c-p-i-o

@pytorch-bot
Copy link

pytorch-bot bot commented Mar 26, 2025 •
edited
Loading

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/150040

Note: Links to docs will display an error until the docs builds have been completed.

❌ 5 New Failures, 1 Cancelled Job, 2 Unrelated Failures

As of commit 58fb59d with merge base 8d08b49 (image):

NEW FAILURES - The following jobs have failed:

CANCELLED JOB - The following job was cancelled. Please retry:

FLAKY - The following jobs failed but were likely due to flakiness present on trunk:

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@pytorch-bot pytorch-bot bot added oncall: distributed Add this issue/PR to distributed oncall triage queue topic: not user facing topic category labels Mar 26, 2025
kwen2501 added a commit that referenced this pull request Mar 26, 2025
@kwen2501
[c10d] Strengthen CUDA Graph test
7144ead 
ghstack-source-id: 93d4992
Pull Request resolved: #150040
@kwen2501 kwen2501 changed the title [c10d] Strengthen CUDA Graph test [c10d] Test multiple CUDA Graph captures May 6, 2025
@kwen2501
Copy link
Collaborator Author

kwen2501 commented May 6, 2025

@pytorchbot merge

@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label May 6, 2025
@pytorchmergebot
Copy link
Collaborator

pytorchmergebot commented May 6, 2025

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging
Check the merge workflow status
here

@pytorchmergebot
Copy link
Collaborator

pytorchmergebot commented May 6, 2025

Merge failed

Reason: 1 mandatory check(s) failed. The first few are:

Dig deeper by viewing the failures on hud

Details for Dev Infra team Raised by workflow job

Failing merge rule: Core Maintainers

@kwen2501
Copy link
Collaborator Author

kwen2501 commented May 8, 2025

@pytorchbot merge -f "Failures are unrelated"

@pytorchmergebot
Copy link
Collaborator

pytorchmergebot commented May 8, 2025

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging
Check the merge workflow status
here

@github-actions github-actions bot deleted the gh/kwen2501/136/head branch June 12, 2025 02:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@fduwjj fduwjj fduwjj approved these changes

Assignees

No one assigned

Labels

ciflow/trunk Trigger trunk jobs on your pull request Merged oncall: distributed Add this issue/PR to distributed oncall triage queue topic: not user facing topic category

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@kwen2501 @pytorchmergebot @fduwjj