Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[CD] Deprecate CUDA 12.8 builds in favor of CUDA 13.0#179072

Closed
tinglvv wants to merge 1 commit into
pytorch:mainfrom
tinglvv:deprecate-128-builds
Closed

[CD] Deprecate CUDA 12.8 builds in favor of CUDA 13.0#179072
tinglvv wants to merge 1 commit into
pytorch:mainfrom
tinglvv:deprecate-128-builds

Conversation

@tinglvv
Copy link
Copy Markdown
Collaborator

@tinglvv tinglvv commented Apr 1, 2026

Remove CUDA 12.8 from the binary build matrix and regenerate nightly workflows. CUDA 13.0 is already the stable version, making 12.8 redundant.

#178665

@tinglvv tinglvv requested a review from a team as a code owner April 1, 2026 22:16
@pytorch-bot
Copy link
Copy Markdown

pytorch-bot Bot commented Apr 1, 2026

🔗 Helpful Links

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

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

❌ 1 New Failure, 31 Pending, 1 Unrelated Failure

As of commit b130b51 with merge base a74f52b (image):

NEW FAILURE - The following job has failed:

FLAKY - The following job failed but was likely due to flakiness present on trunk:

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

@pytorch-bot pytorch-bot Bot added the topic: not user facing topic category label Apr 1, 2026
@tinglvv tinglvv added the ciflow/binaries Trigger all binary build and upload jobs on the PR label Apr 1, 2026
@soulitzer soulitzer added the triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module label Apr 2, 2026
@tinglvv
Copy link
Copy Markdown
Collaborator Author

tinglvv commented Apr 2, 2026

@pytorchbot rebase

@pytorchmergebot
Copy link
Copy Markdown
Collaborator

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

@pytorchmergebot
Copy link
Copy Markdown
Collaborator

Successfully rebased deprecate-128-builds onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via git checkout deprecate-128-builds && git pull --rebase)

Copy link
Copy Markdown
Collaborator

@atalman atalman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Remove CUDA 12.8 from the binary build matrix and regenerate nightly
workflows. CUDA 13.0 is already the stable version, making 12.8
redundant.
@tinglvv tinglvv force-pushed the deprecate-128-builds branch from 6dd352f to b130b51 Compare April 7, 2026 21:57
@atalman
Copy link
Copy Markdown
Collaborator

atalman commented Apr 8, 2026

@pytorchmergebot merge -f "lint and other workflows look good"

@pytorchmergebot
Copy link
Copy Markdown
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

pytorchmergebot pushed a commit that referenced this pull request May 4, 2026
## Summary

The release-to-CC dict in \`torch/cuda/__init__.py\` drove the *\"install a PyTorch release that supports one of these CUDA versions: ...\"* recommendation, but had drifted from the actual binary build matrix:

- **\"12.6\"** was missing CC \`7.5\` — `.ci/manywheel/build_cuda.sh` puts 7.5 in the base list for every release.
- **\"12.8\"** was deprecated in #179072 (replaced by 13.0). Recommending it is misleading and was the proximate cause of #182250.
- **\"13.2\"** was missing entirely even though it's in `CUDA_ARCHES` today.

That stale data caused the V100 false-positive in #182250 — `cu128` was recommended for a CC 7.0 device, but the actual `cu128` wheel had been built without `sm_70` (arch list \`7.5;8.0;8.6;9.0;10.0;12.0\`).

This PR updates the dict to match the union of x86_64 and aarch64 `TORCH_CUDA_ARCH_LIST` in `.ci/manywheel/build_cuda.sh` (the build-time source of truth), and adds a comment pointing readers there so the next \`CUDA_ARCHES\` change knows what else to bump.

Authored with Claude.
Pull Request resolved: #182358
Approved by: https://github.com/malfet
atalman added a commit that referenced this pull request May 4, 2026
Fix stale PYTORCH_RELEASES_CODE_CC dict (fixes #182250) (#182358)

## Summary

The release-to-CC dict in \`torch/cuda/__init__.py\` drove the *\"install a PyTorch release that supports one of these CUDA versions: ...\"* recommendation, but had drifted from the actual binary build matrix:

- **\"12.6\"** was missing CC \`7.5\` — `.ci/manywheel/build_cuda.sh` puts 7.5 in the base list for every release.
- **\"12.8\"** was deprecated in #179072 (replaced by 13.0). Recommending it is misleading and was the proximate cause of #182250.
- **\"13.2\"** was missing entirely even though it's in `CUDA_ARCHES` today.

That stale data caused the V100 false-positive in #182250 — `cu128` was recommended for a CC 7.0 device, but the actual `cu128` wheel had been built without `sm_70` (arch list \`7.5;8.0;8.6;9.0;10.0;12.0\`).

This PR updates the dict to match the union of x86_64 and aarch64 `TORCH_CUDA_ARCH_LIST` in `.ci/manywheel/build_cuda.sh` (the build-time source of truth), and adds a comment pointing readers there so the next \`CUDA_ARCHES\` change knows what else to bump.

Authored with Claude.
Pull Request resolved: #182358
Approved by: https://github.com/malfet

(cherry picked from commit f45ab9e)

Co-authored-by: atalman <[email protected]>
Alokksinha00 pushed a commit to Alokksinha00/pytorch that referenced this pull request May 15, 2026
…ch#182358)

## Summary

The release-to-CC dict in \`torch/cuda/__init__.py\` drove the *\"install a PyTorch release that supports one of these CUDA versions: ...\"* recommendation, but had drifted from the actual binary build matrix:

- **\"12.6\"** was missing CC \`7.5\` — `.ci/manywheel/build_cuda.sh` puts 7.5 in the base list for every release.
- **\"12.8\"** was deprecated in pytorch#179072 (replaced by 13.0). Recommending it is misleading and was the proximate cause of pytorch#182250.
- **\"13.2\"** was missing entirely even though it's in `CUDA_ARCHES` today.

That stale data caused the V100 false-positive in pytorch#182250 — `cu128` was recommended for a CC 7.0 device, but the actual `cu128` wheel had been built without `sm_70` (arch list \`7.5;8.0;8.6;9.0;10.0;12.0\`).

This PR updates the dict to match the union of x86_64 and aarch64 `TORCH_CUDA_ARCH_LIST` in `.ci/manywheel/build_cuda.sh` (the build-time source of truth), and adds a comment pointing readers there so the next \`CUDA_ARCHES\` change knows what else to bump.

Authored with Claude.
Pull Request resolved: pytorch#182358
Approved by: https://github.com/malfet
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ciflow/binaries Trigger all binary build and upload jobs on the PR Merged open source topic: not user facing topic category triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants