Skip to content

Conversation

atalman
Copy link
Contributor

@atalman atalman commented Sep 22, 2025

Please see build script:

13.0)
TORCH_CUDA_ARCH_LIST="7.5;8.0;8.6;9.0;10.0;12.0+PTX"
;;

This should display correct warning:
Please install PyTorch with a following CUDA configurations: 12.6 12.8 13.0 following instructions at https://pytorch.org/get-started/locally/

Copy link

pytorch-bot bot commented Sep 22, 2025

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/163585

Note: Links to docs will display an error until the docs builds have been completed.

✅ No Failures

As of commit 2a01921 with merge base 8da0086 (image):
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@atalman atalman changed the title CUDA 13.0 Warning update CUDA 13.0 Warning update for supported architectures Sep 22, 2025
@atalman atalman added the topic: not user facing topic category label Sep 22, 2025
@seemethere
Copy link
Member

Can this have more context as to why we're doing this?

@atalman
Copy link
Contributor Author

atalman commented Sep 22, 2025

@seemethere This will display warning if we try to execute CUDA 13.0 build on machine that is outside of the range: 7.5;8.0;8.6;9.0;10.0;12.0

@atalman
Copy link
Contributor Author

atalman commented Sep 23, 2025

@pytorchmergebot merge -f "all required tests are passing"

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging
Check the merge workflow status
here

@atalman
Copy link
Contributor Author

atalman commented Sep 23, 2025

@pytorchbot cherry-pick --onto release/2.9 -c critical

pytorchbot pushed a commit that referenced this pull request Sep 23, 2025
Please see build script: https://github.com/pytorch/pytorch/blob/8da008678fcb95dbf55a33451136a242871ae4e2/.ci/manywheel/build_cuda.sh#L69-L71

This should display correct warning:
``
Please install PyTorch with a following CUDA
configurations: 12.6 12.8 13.0 following instructions at
https://pytorch.org/get-started/locally/
``
Pull Request resolved: #163585
Approved by: https://github.com/malfet

(cherry picked from commit 3c64b2a)
@pytorchbot
Copy link
Collaborator

Cherry picking #163585

The cherry pick PR is at #163633 and it is recommended to link a critical cherry pick PR with an issue. The following tracker issues are updated:

Details for Dev Infra team Raised by workflow job

Camyll pushed a commit that referenced this pull request Sep 23, 2025
CUDA 13.0 Warning update for supported architectures (#163585)

Please see build script: https://github.com/pytorch/pytorch/blob/8da008678fcb95dbf55a33451136a242871ae4e2/.ci/manywheel/build_cuda.sh#L69-L71

This should display correct warning:
``
Please install PyTorch with a following CUDA
configurations: 12.6 12.8 13.0 following instructions at
https://pytorch.org/get-started/locally/
``
Pull Request resolved: #163585
Approved by: https://github.com/malfet

(cherry picked from commit 3c64b2a)

Co-authored-by: atalman <atalman@fb.com>
dsashidh pushed a commit to dsashidh/pytorch that referenced this pull request Sep 26, 2025
Please see build script: https://github.com/pytorch/pytorch/blob/8da008678fcb95dbf55a33451136a242871ae4e2/.ci/manywheel/build_cuda.sh#L69-L71

This should display correct warning:
``
Please install PyTorch with a following CUDA
configurations: 12.6 12.8 13.0 following instructions at
https://pytorch.org/get-started/locally/
``
Pull Request resolved: pytorch#163585
Approved by: https://github.com/malfet
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants