-
Notifications
You must be signed in to change notification settings - Fork 26.3k
[dtensor][7/N] remove backend in with_comms #93040
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
backend is not actually getting used in anywhere, so we remove the backend option [ghstack-poisoned]
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/93040
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 91ca742: This comment was automatically generated by Dr. CI and updates every 15 minutes. |
backend is not actually getting used in anywhere, so we remove the backend option [ghstack-poisoned]
backend is not actually getting used in anywhere, so we remove the backend option [ghstack-poisoned]
wz337
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
backend is not actually getting used in anywhere, so we remove the backend option [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 |
Stack from ghstack (oldest at bottom):
backend is not actually getting used in anywhere, so we remove the
backend option