[Gasoonjia]

Summary

PyTorch no longer publishes cu126 nightlies. The torchao cu126 channel stops at 0.19.0.dev20260907, so the 12.6 CI rows can't install the current pins. This removes CUDA 12.6 support.

Support

• install_utils.py: remove (12, 6) from SUPPORTED_CUDA_VERSIONS. Supported versions are now 13.0, 13.2, 13.4.

CI

• .github/workflows/vulkan.yml: move test-vulkan-nvidia and the Vulkan LLM e2e job from the cuda12.6 image to cuda13.2. The pytorch/almalinux-builder:cuda13.2 image exists and is current.
• .github/workflows/cuda.yml: drop 12.6 from the test-cuda-builds matrix. Coverage that remains:
  • build matrix rows for 13.0 and 13.4
  • 13.0 on every model e2e / benchmark job (10+ jobs)
  • 13.2 on the Windows e2e jobs (cuda-windows.yml) and the published wheel rows (filter_cuda_matrix.py: cu132 / cu134)
• .ci/scripts/wheel/cuda_arch_list.sh: remove the cu126 GPU arch lists. A cu126 row now fails as an unknown train.
• .ci/docker/common/install_cuda_windows_cross_compile.sh: remove the 12.6 entry.
• .ci/scripts/tests/test_cuda_workflow.py, .ci/scripts/tests/test_cu134_dependencies.py: drop the 12.6 cases.

Docs / comments

• docs/source/backends/cuda/cuda-overview.md: the source build now lists CUDA 13.0 instead of 12.6.
• Update the 12.6 / cu126 examples in install_utils.py, setup.py, filter_cuda_matrix.py, test_shared_libraries.py, cuda_benchmark.py.

Intentionally unchanged

• backends/cuda/cuda_backend.py _setup_cuda_environment_for_fatbin: the CUDA 12 ptxas branch handles any user torch build on CUDA 12.x below 12.9, not just a 12.6 support row.
• setup.py / test_shared_libraries.py CUDA 12 runtime package mapping (nvidia-cuda-runtime-cu12): this is keyed by CUDA major, not 12.6.
• Windows cross-compile entries for 12.8 / 12.9.

Test plan

• pytest .ci/scripts/tests/test_cu134_dependencies.py .ci/scripts/tests/test_cuda_workflow.py .ci/scripts/tests/test_filter_cuda_matrix.py: 49 passed
• executorch_cuda_arch_list: cu130/cu132/cu134 still resolve, cu126 now returns 64 (unknown train)
• Both workflow YAMLs parse; flake8 clean
• Repo-wide grep for 12.6 / cu126 / (12, 6): two hits left, both kept on purpose: the nvidia-cuda-runtime-cu12==12.6.77 example in a parsing comment, and the CUDA 12.6+ comment on the unchanged ptxas branch in cuda_backend.py
• CI (Vulkan real-GPU jobs on the 13.2 image)

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 2 Cancelled Jobs, 4 Unrelated Failures, 2 Unclassified Failures

As of commit 0cc0ce7 with merge base 97971ca ():

UNCLASSIFIED FAILURES - DrCI could not classify the following jobs because the workflow did not run on the merge base. The failures may be pre-existing on trunk or introduced by this PR:

• Core AI / backend-tester (operators, coreai_w8a8) / test-coreai_w8a8-operators (gh) (this job did not run on the merge base, so DrCI cannot tell whether the failure is pre-existing)
  AssertionError: 24 tests failed; at most 23 allowed
• trunk / test-custom-ops-macos (cmake) / macos-job (gh) (this job did not run on the merge base, so DrCI cannot tell whether the failure is pre-existing)
  executorch

CANCELLED JOBS - The following jobs were cancelled. Please retry:

• trunk / test-demo-backend-delegation (buck2) / linux-job (gh)
  [runner-container-hooks] FATAL: received SIGINT
• trunk / test-demo-backend-delegation (cmake) / linux-job (gh)
  [runner-container-hooks] FATAL: received SIGINT

BROKEN TRUNK - The following jobs failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

• Test CUDA Builds / test-muse-glimmer-cuda-e2e-kquant-17gb-dflash-image-batching / linux-job (gh) (trunk failure)
  ##[error]received SIGINT
• trunk / test-arm-backend-vkml (test_pytest_models_vkml) / linux-job (gh) (trunk failure)
  RuntimeError: Command bash /__w/_temp/exec_script failed with exit code 1
• trunk / test-cortex-m-ops / run (cortex-m0plus) / cortex-m-ops-cortex-m0plus (gh) (trunk failure)
  RuntimeError: Command bash /__w/_temp/exec_script failed with exit code 4
• trunk / test-cortex-m-ops / run (cortex-m7) / cortex-m-ops-cortex-m7 (gh) (trunk failure)
  RuntimeError: Command bash /__w/_temp/exec_script failed with exit code 4

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

[github-actions]

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.