8000 [RFC] dropping CUDA 11.8 support in CI/CD · Issue #147383 · pytorch/pytorch · GitHub
[go: up one dir, main page]

Skip to content

[RFC] dropping CUDA 11.8 support in CI/CD #147383

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

Open
atalman opened this issue Feb 18, 2025 · 1 comment
Open

[RFC] dropping CUDA 11.8 support in CI/CD #147383

atalman opened this issue Feb 18, 2025 · 1 comment
Labels
module: build Build system issues module: cuda Related to torch.cuda, and CUDA support in general triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module

Comments

@atalman
Copy link
Contributor
atalman commented Feb 18, 2025

Related to: #145544

Opening this RFC to discuss dropping of CUDA 11.8 possibility and timeline

For PyTorch Release 2.7 we are proceeding with following configuration:
CUDA 11.8, CUDNN 9.1.0.70 - Same as Previous Release 2.6. No changes to CUDA 11.8 - Legacy version
CUDA 12.6 CUDNN 9.x - Version Released to Pypi - Stable version
CUDA 12.8 CUDNN 9.x - New Experimental version

Proposal is to announce removal of CUDA 11.8 at release 2.7 and drop it for release 2.8. Hence dropping support of 11.8 in nightlies for Mar 2025-Jun 2025.

cc @malfet @seemethere @ptrblck @msaroufim @eqy @tinglvv @nWEIdia

Versions

2.7-2.8

@atalman atalman changed the title [RFC] CUDA 11.8 support [RFC] dropping CUDA 11.8 support Feb 18, 2025
@colesbury colesbury added module: build Build system issues module: cuda Related to torch.cuda, and CUDA support in general triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module labels Feb 18, 2025
@atalman atalman changed the title [RFC] dropping CUDA 11.8 support [RFC] dropping CUDA 11.8 support in CI/CD Mar 10, 2025
@zpcore
Copy link
< 8000 /div>
Contributor
zpcore commented Apr 8, 2025

Hi @miladm , @ysiraichi , CUDA 11.8 is already legacy status. I think we can drop 11.8 for PyTorch/XLA 2.7 release then.

pytorchmergebot pushed a commit that referenced this issue May 20, 2025
… to cu126-sm75 (#151594)

This PR moves distributed cuda CI job from cuda 11.8 to cuda 12.6.
In doing so, a few unit test failures were exposed, some if not all of which would take a while to root-cause and fix, so temporarily skip them after creating the issues.

#153479 test_nan_assert tricky behavior (e.g. skip_but_pass_in_sandcastle, ubuntu 20.04 does not work, ubuntu 22.04 works, Amazon Linux 2023 skip - what is Sandcastle OS?)
#153122 CUDA context related
#153517  NCCL regression, future NCCL may fix it

See: #147383

Pull Request resolved: #151594
Approved by: https://github.com/eqy, https://github.com/atalman, https://github.com/cyyever
pytorchmergebot pushed a commit that referenced this issue May 22, 2025
…12.6 (#151594)

This PR moves distributed cuda CI job from cuda 11.8 to cuda 12.6.
In doing so, a few unit test failures were exposed, some if not all of which would take a while to root-cause and fix, so temporarily skip them after creating the issues.

#153479 test_nan_assert tricky behavior (e.g. skip_but_pass_in_sandcastle, ubuntu 20.04 does not work, ubuntu 22.04 works, Amazon Linux 2023 skip - what is Sandcastle OS?)
#153122 CUDA context related
#153517  NCCL regression, future NCCL may fix it
#154073 skip test_symmetric_memory for cuda 12.6 before it is fixed

See: #147383

Pull Request resolved: #151594
Approved by: https://github.com/eqy, https://github.com/atalman, https://github.com/cyyever, https://github.com/huydhn, https://github.com/kwen2501
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
module: build Build system issues module: cuda Related to torch.cuda, and CUDA support in general triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module
Projects
None yet
Development

No branches or pull requests

3 participants
0