-
Notifications
You must be signed in to change notification settings - Fork 25.7k
[CD] Build libtorch without nvshmem #160910
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
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/160910
Note: Links to docs will display an error until the docs builds have been completed. ⏳ No Failures, 2 PendingAs of commit 94a7aeb with merge base 1795116 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
It was done once for cuSparseLT, now it's nvShmem's time Fixes #160762 [ghstack-poisoned]
|
@pytorchbot merge -f "Lint + libtorch builds are green" |
Merge startedYour change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
It was done once for cuSparseLT in pytorch/builder@f01d710 , now it's nvShmem's time Fixes pytorch#160762 Pull Request resolved: pytorch#160910 Approved by: https://github.com/Skylion007
It was done once for cuSparseLT in pytorch/builder@f01d710 , now it's nvShmem's time Fixes pytorch#160762 Pull Request resolved: pytorch#160910 Approved by: https://github.com/Skylion007
Stack from ghstack (oldest at bottom):
It was done once for cuSparseLT in pytorch/builder@f01d710 , now it's nvShmem's time
Fixes #160762