-
Notifications
You must be signed in to change notification settings - Fork 24.7k
[CUDA][CUBLAS] Explicitly link against cuBLASLt
#95094
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/95094
Note: Links to docs will display an error until the docs builds have been completed. ❗ 1 Active SEVsThere are 1 currently active SEVs. If your PR is affected, please view them below: ✅ No FailuresAs of commit 5f4ad94: This comment was automatically generated by Dr. CI and updates every 15 minutes. |
CC @atalman @malfet as we've just discussed it. A bit more information:
Might also be related to #91067 although we have not verified it yet. |
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.
Sure, we should do it
cc @peterbell10 |
@pytorchmergebot rebase |
@pytorchbot successfully started a rebase job. Check the current status here |
Successfully rebased |
d4db126
to
0895248
Compare
A lot of failing tests (30+) but it seems all of them fail with either:
or
@eqy could you try another rebase to re-trigger the CI? |
@pytorchmergebot rebase |
@pytorchbot successfully started a rebase job. Check the current status here |
Successfully rebased |
0895248
to
d334015
Compare
@pytorchmergebot rebase |
@pytorchbot successfully started a rebase job. Check the current status here |
Successfully rebased |
d334015
to
c60b190
Compare
Some Windows builds fail with:
which seems to be related to #95170. |
@pytorchmergebot rebase |
@pytorchbot successfully started a rebase job. Check the current status here |
Successfully rebased |
c60b190
to
5ff816b
Compare
@pytorchmergebot rebase |
@pytorchbot successfully started a rebase job. Check the current status here |
Successfully rebased |
5ff816b
to
94a8b68
Compare
@pytorchmergebot rebase |
@pytorchbot successfully started a rebase job. Check the current status here |
Successfully rebased |
94a8b68
to
5f4ad94
Compare
@pytorchmergebot -f "all required tests are green" |
❌ 🤖 pytorchbot command failed:
Try |
@pytorchmergebot merge -f "all required tests are green" |
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 |
An issue surfaced recently that revealed that we were never explicitly linking against `cuBLASLt`, this fixes it by linking explicitly rather than depending on linker magic. CC @ptrblck @ngimel Pull Request resolved: pytorch/pytorch#95094 Approved by: https://github.com/malfet, https://github.com/ngimel, https://github.com/atalman
An issue surfaced recently that revealed that we were never explicitly linking against `cuBLASLt`, this fixes it by linking explicitly rather than depending on linker magic. CC @ptrblck @ngimel Pull Request resolved: pytorch/pytorch#95094 Approved by: https://github.com/malfet, https://github.com/ngimel, https://github.com/atalman
An issue surfaced recently that revealed that we were never explicitly linking against `cuBLASLt`, this fixes it by linking explicitly rather than depending on linker magic. CC @ptrblck @ngimel Pull Request resolved: pytorch#95094 Approved by: https://github.com/malfet, https://github.com/ngimel, https://github.com/atalman
An issue surfaced recently that revealed that we were never explicitly linking against `cuBLASLt`, this fixes it by linking explicitly rather than depending on linker magic. CC @ptrblck @ngimel Pull Request resolved: #95094 Approved by: https://github.com/malfet, https://github.com/ngimel, https://github.com/atalman Co-authored-by: eqy <eddiey@nvidia.com>
An issue surfaced recently that revealed that we were never explicitly linking against `cuBLASLt`, this fixes it by linking explicitly rather than depending on linker magic. CC @ptrblck @ngimel Pull Request resolved: pytorch/pytorch#95094 Approved by: https://github.com/malfet, https://github.com/ngimel, https://github.com/atalman
)" This reverts commit cc39cd6.
An issue surfaced recently that revealed that we were never explicitly linking against
cuBLASLt
, this fixes it by linking explicitly rather than depending on linker magic.CC @ptrblck @ngimel