-
Notifications
You must be signed in to change notification settings - Fork 24.7k
Set USE_CUFILE=1 by default and add pypi package to binary build matrix #145748
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
Set USE_CUFILE=1 by default and add pypi package to binary build matrix #145748
Conversation
[ghstack-poisoned]
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/145748
Note: Links to docs will display an error until the docs builds have been completed. ❌ 10 New Failures, 1 Pending, 2 Unrelated FailuresAs of commit fe806a1 with merge base b60f630 ( NEW FAILURES - The following jobs have failed:
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. |
… build matrix" [ghstack-poisoned]
… build matrix" [ghstack-poisoned]
… build matrix" [ghstack-poisoned]
… build matrix" [ghstack-poisoned]
… build matrix" [ghstack-poisoned]
… build matrix" [ghstack-poisoned]
… build matrix" [ghstack-poisoned]
… build matrix" [ghstack-poisoned]
The merge job was canceled or timed out. This most often happen if two merge requests were issued for the same PR, or if merge job was waiting for more than 6 hours for tests to finish. In later case, please do not hesitate to reissue the merge command |
@pytorchbot merge -f |
❌ 🤖 pytorchbot command failed:
Try |
@pytorchbot merge -f "rocm flaky + rocm distributed queued overnight" |
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 |
Follow up to #145748 [ghstack-poisoned]
Follow up to #145748 [ghstack-poisoned]
Follow up to #145748 [ghstack-poisoned]
Follow up to #145748 that turned USE_CUFILE on for CUDA 12.6 and 12.8 binaries [ghstack-poisoned]
Follow up to #145748 that turned USE_CUFILE on for CUDA 12.6 and 12.8 binaries [ghstack-poisoned]
Follow up to #145748 that turned USE_CUFILE on for CUDA 12.6 and 12.8 binaries [ghstack-poisoned]
Follow up to #145748 that turned USE_CUFILE on for CUDA 12.6 and 12.8 binaries [ghstack-poisoned]
Follow up to #145748 that turned USE_CUFILE on for CUDA 12.6 and 12.8 binaries [ghstack-poisoned]
Follow up to #145748 that turned USE_CUFILE on for CUDA 12.6 and 12.8 binaries [ghstack-poisoned]
Follow up to #145748 that turned USE_CUFILE on for CUDA 12.6 and 12.8 binaries [ghstack-poisoned]
Follow up to #145748 that turned USE_CUFILE on for CUDA 12.6 and 12.8 binaries Pull Request resolved: #147120 Approved by: https://github.com/albanD
…ix (#145748) Pull Request resolved: #145748 Approved by: https://github.com/atalman
Follow up to #145748 that turned USE_CUFILE on for CUDA 12.6 and 12.8 binaries Pull Request resolved: #147120 Approved by: https://github.com/albanD
ghstack-source-id: accb2c7 Pull Request resolved: pytorch/pytorch#145748
…ix (pytorch#145748) Pull Request resolved: pytorch#145748 Approved by: https://github.com/atalman
Follow up to pytorch#145748 that turned USE_CUFILE on for CUDA 12.6 and 12.8 binaries Pull Request resolved: pytorch#147120 Approved by: https://github.com/albanD
Stack from ghstack (oldest at bottom):