-
Notifications
You must be signed in to change notification settings - Fork 26.3k
[c10d] update alltoall signature to be more consistent #90569
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
alltoall signature should be more consistent with its argument updated and this should be a BC breaking change [ghstack-poisoned]
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/90569
Note: Links to docs will display an error until the docs builds have been completed. ❌ 2 FailuresAs of commit 26f3fb2: The following jobs have failed:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
alltoall signature should be more consistent with its argument updated and this should be a BC breaking change cc ezyang gchanan [ghstack-poisoned]
|
@pytorchbot merge |
Merge startedYour 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 |
Merge failedReason: Command Details for Dev Infra teamRaised by workflow job |
alltoall signature should be more consistent with its argument updated and this should be a BC breaking change cc ezyang gchanan [ghstack-poisoned]
alltoall signature should be more consistent with its argument updated and this should be a BC breaking change cc ezyang gchanan [ghstack-poisoned]
alltoall signature should be more consistent with its argument updated and this should be a BC breaking change cc ezyang gchanan [ghstack-poisoned]
|
@pytorchbot merge |
Merge startedYour 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 |
Merge failedReason: The following mandatory check(s) failed (Rule Dig deeper by viewing the failures on hud Details for Dev Infra teamRaised by workflow job |
|
@pytorchbot merge -f "failures not related" |
Merge startedYour change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Stack from ghstack (oldest at bottom):
alltoall signature should be more consistent with its argument
updated and this should be a BC breaking change
cc @ezyang @gchanan