[CD] CUDA 13 specific followup changes by tinglvv · Pull Request #162455 · pytorch/pytorch

tinglvv · 2025-09-09T04:13:23Z

Follow up for CUDA 13 bring up #159779
sm50-70 should not be added to sbsa build arch list, as previous archs had no support for arm.
remove platform_machine from PYTORCH_EXTRA_INSTALL_REQUIREMENTS

cc @atalman @malfet @ptrblck @nWEIdia

pytorch-bot · 2025-09-09T04:13:26Z

🔗 Helpful Links

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

📄 Preview Python docs built from this PR
📄 Preview C++ docs built from this PR
❓ Need help or want to give feedback on the CI? Visit the bot commands wiki

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

❌ 7 New Failures, 2 Cancelled Jobs, 51 Pending

As of commit 2c5c1b3 with merge base b5e6e58 ():

NEW FAILURES - The following jobs have failed:

linux-s390x-binary-manywheel / manywheel-py3_10-cpu-s390x-build / build (gh)
undefined reference to 'dlclose'
linux-s390x-binary-manywheel / manywheel-py3_11-cpu-s390x-build / build (gh)
undefined reference to 'dlclose'
linux-s390x-binary-manywheel / manywheel-py3_12-cpu-s390x-build / build (gh)
undefined reference to 'dlclose'
linux-s390x-binary-manywheel / manywheel-py3_13-cpu-s390x-build / build (gh)
undefined reference to 'dlclose'
linux-s390x-binary-manywheel / manywheel-py3_13t-cpu-s390x-build / build (gh)
undefined reference to 'dlclose'
linux-s390x-binary-manywheel / manywheel-py3_14-cpu-s390x-build / build (gh)
undefined reference to 'dlclose'
linux-s390x-binary-manywheel / manywheel-py3_14t-cpu-s390x-build / build (gh)
undefined reference to 'dlclose'

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

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

.github/scripts/generate_binary_build_matrix.py

tinglvv · 2025-09-09T23:27:55Z

The failure is irrelevant

2025-09-09T22:47:36.4532587Z FAILED [0.1411s] dynamo/cpython/3_13/test_collections.py::TestNamedTuple::test_namedtuple_subclass_issue_24931 - RuntimeError: Unexpected success, please remove `test/dynamo_expected_failures/CPython313-test_collections-TestNamedTuple.test_namedtuple_subclass_issue_24931

atalman · 2025-09-09T23:29:14Z

@tinglvv for sm50-70 should not be added to sbsa build arch list, as previous archs had no support for arm. Do we have some kind of Nvidia doc specifying list of arches supported on aarch64 builds for different CUDA versions ? Please comment with details: #162455

tinglvv · 2025-09-10T16:36:22Z

@tinglvv for sm50-70 should not be added to sbsa build arch list, as previous archs had no support for arm. Do we have some kind of Nvidia doc specifying list of arches supported on aarch64 builds for different CUDA versions ? Please comment with details: #162455

Sorry while there seems to be no original doc that specifies it, our testing for SBSA started from Ampere and there was no support for sm50-75 for SBSA wheels existed. Therefore we hope to keep the same support matrix for CUDA 12 as CUDA 13 to start from sm_80.

tinglvv · 2025-09-10T19:53:10Z

@pytorchbot rebase

pytorchmergebot · 2025-09-10T19:54:39Z

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

pytorchmergebot · 2025-09-10T19:54:42Z

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

atalman · 2025-09-11T00:00:05Z

@pytorchmergebot merge -f "change looks good, merging"

pytorchmergebot · 2025-09-11T00:03:35Z

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

Follow up for CUDA 13 bring up pytorch#159779 sm50-70 should not be added to sbsa build arch list, as previous archs had no support for arm. remove platform_machine from PYTORCH_EXTRA_INSTALL_REQUIREMENTS Pull Request resolved: pytorch#162455 Approved by: https://github.com/atalman

atalman · 2025-09-23T16:49:59Z

@pytorchbot cherry-pick --onto release/2.9 --fixes "Critical binary build fix" -c critical

pytorchbot · 2025-09-23T16:55:08Z

Cherry picking #162455

Command git -C /home/runner/work/pytorch/pytorch cherry-pick -x bb1d53bc47109c7c97e5fa072280d05b04e023e5 returned non-zero exit code 1

Auto-merging .ci/aarch64_linux/aarch64_ci_build.sh
Auto-merging .ci/aarch64_linux/aarch64_wheel_ci_build.py
Auto-merging .github/scripts/generate_binary_build_matrix.py
CONFLICT (content): Merge conflict in .github/scripts/generate_binary_build_matrix.py
Auto-merging .github/workflows/generated-linux-aarch64-binary-manywheel-nightly.yml
CONFLICT (content): Merge conflict in .github/workflows/generated-linux-aarch64-binary-manywheel-nightly.yml
Auto-merging .github/workflows/generated-linux-binary-manywheel-main.yml
CONFLICT (content): Merge conflict in .github/workflows/generated-linux-binary-manywheel-main.yml
Auto-merging .github/workflows/generated-linux-binary-manywheel-nightly.yml
CONFLICT (content): Merge conflict in .github/workflows/generated-linux-binary-manywheel-nightly.yml
error: could not apply bb1d53bc471... [CD] CUDA 13 specific followup changes (#162455)
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".
hint: Disable this message with "git config set advice.mergeConflict false"

Details for Dev Infra team

Raised by workflow job

Follow up for CUDA 13 bring up pytorch#159779 sm50-70 should not be added to sbsa build arch list, as previous archs had no support for arm. remove platform_machine from PYTORCH_EXTRA_INSTALL_REQUIREMENTS Pull Request resolved: pytorch#162455 Approved by: https://github.com/atalman

…From CUDA 12.6 and CUDA 12.8 builds (#162455) (#163764) * [CD] CUDA 13 specific followup changes (#162455) Follow up for CUDA 13 bring up #159779 sm50-70 should not be added to sbsa build arch list, as previous archs had no support for arm. remove platform_machine from PYTORCH_EXTRA_INSTALL_REQUIREMENTS Pull Request resolved: #162455 Approved by: https://github.com/atalman * update --------- Co-authored-by: Ting Lu <tingl@nvidia.com>

Follow up for CUDA 13 bring up pytorch#159779 sm50-70 should not be added to sbsa build arch list, as previous archs had no support for arm. remove platform_machine from PYTORCH_EXTRA_INSTALL_REQUIREMENTS Pull Request resolved: pytorch#162455 Approved by: https://github.com/atalman

Signed-off-by: Huy Do <huydhn@gmail.com>

When trying to bring cu129 back in #163029, I mainly looked at #163029 and missed another tweak coming from #162455 I discover this issue when testing aarch64+cu129 builds in https://github.com/pytorch/test-infra/actions/runs/18603342105/job/53046883322?pr=7373. Surprisingly, there is no test running for aarch64 CUDA build from what I see in https://hud.pytorch.org/pytorch/pytorch/commit/79a37055e790482c12bf32e69b28c8e473d0209d. Pull Request resolved: #165794 Approved by: https://github.com/malfet

When trying to bring cu129 back in #163029, I mainly looked at #163029 and missed another tweak coming from #162455 I discover this issue when testing aarch64+cu129 builds in https://github.com/pytorch/test-infra/actions/runs/18603342105/job/53046883322?pr=7373. Surprisingly, there is no test running for aarch64 CUDA build from what I see in https://hud.pytorch.org/pytorch/pytorch/commit/79a37055e790482c12bf32e69b28c8e473d0209d. Pull Request resolved: #165794 Approved by: https://github.com/malfet (cherry picked from commit 9095a9d)

[CD] Apply the fix from #162455 to aarch64+cu129 build (#165794) When trying to bring cu129 back in #163029, I mainly looked at #163029 and missed another tweak coming from #162455 I discover this issue when testing aarch64+cu129 builds in https://github.com/pytorch/test-infra/actions/runs/18603342105/job/53046883322?pr=7373. Surprisingly, there is no test running for aarch64 CUDA build from what I see in https://hud.pytorch.org/pytorch/pytorch/commit/79a37055e790482c12bf32e69b28c8e473d0209d. Pull Request resolved: #165794 Approved by: https://github.com/malfet (cherry picked from commit 9095a9d) Co-authored-by: Huy Do <huydhn@gmail.com>

…h#165794) When trying to bring cu129 back in pytorch#163029, I mainly looked at pytorch#163029 and missed another tweak coming from pytorch#162455 I discover this issue when testing aarch64+cu129 builds in https://github.com/pytorch/test-infra/actions/runs/18603342105/job/53046883322?pr=7373. Surprisingly, there is no test running for aarch64 CUDA build from what I see in https://hud.pytorch.org/pytorch/pytorch/commit/79a37055e790482c12bf32e69b28c8e473d0209d. Pull Request resolved: pytorch#165794 Approved by: https://github.com/malfet

tinglvv requested a review from a team as a code owner September 9, 2025 04:13

pytorch-bot bot added the release notes: releng release notes category label Sep 9, 2025

tinglvv changed the title ~~[CD] Rm sm50-70 for sbsa and remove platform_machine for PYTORCH_EXTRA_INSTALL_REQUIREMENTS~~ [CD] CUDA 13 specific followup changes Sep 9, 2025

tinglvv added the ciflow/binaries Trigger all binary build and upload jobs on the PR label Sep 9, 2025

pytorchbot added the open source label Sep 9, 2025

atalman reviewed Sep 9, 2025

View reviewed changes

.github/scripts/generate_binary_build_matrix.py Outdated Show resolved Hide resolved

bdhirsh added the triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module label Sep 9, 2025

atalman approved these changes Sep 9, 2025

View reviewed changes

tinglvv force-pushed the cu130-followup branch from f64e04e to 3d0d9d6 Compare September 9, 2025 21:51

tinglvv added 3 commits September 10, 2025 19:54

Rm sm50-70 for sbsa and remove platform_machine for install_requirements

a0fcdb0

remove the platform_machine for 12.6 and 12.8

17fdeec

sync the nvshmem change

2c5c1b3

pytorchmergebot force-pushed the cu130-followup branch from 9849956 to 2c5c1b3 Compare September 10, 2025 19:54

pytorchmergebot added the merging label Sep 11, 2025

pytorchmergebot closed this in bb1d53b Sep 11, 2025

pytorchmergebot added Merged and removed merging labels Sep 11, 2025

This was referenced Sep 24, 2025

[Cherry-Pick] [CD] CUDA 13 specific followup changes. Remove sm50-70 From CUDA 12.6 and CUDA 12.8 builds (#162455) #163764

Merged

[v.2.9.0] Release Tracker #162497

Closed

huydhn added a commit to huydhn/pytorch that referenced this pull request Oct 17, 2025

[CD] Apply the fix from pytorch#162455 to aarch64+cu129 build

088794a

Signed-off-by: Huy Do <huydhn@gmail.com>

huydhn mentioned this pull request Oct 17, 2025

[CD] Apply the fix from #162455 to aarch64+cu129 build #165794

Closed

pytorchbot mentioned this pull request Oct 18, 2025

[CD] Apply the fix from #162455 to aarch64+cu129 build #165819

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[CD] CUDA 13 specific followup changes#162455

[CD] CUDA 13 specific followup changes#162455
tinglvv wants to merge 3 commits intopytorch:mainfrom
tinglvv:cu130-followup

tinglvv commented Sep 9, 2025 •

edited

Loading

Uh oh!

pytorch-bot bot commented Sep 9, 2025 •

edited

Loading

Uh oh!

Uh oh!

tinglvv commented Sep 9, 2025

Uh oh!

atalman commented Sep 9, 2025

Uh oh!

tinglvv commented Sep 10, 2025

Uh oh!

tinglvv commented Sep 10, 2025

Uh oh!

pytorchmergebot commented Sep 10, 2025

Uh oh!

pytorchmergebot commented Sep 10, 2025

Uh oh!

atalman commented Sep 11, 2025

Uh oh!

pytorchmergebot commented Sep 11, 2025

Uh oh!

atalman commented Sep 23, 2025

Uh oh!

pytorchbot commented Sep 23, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

Conversation

tinglvv commented Sep 9, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

pytorch-bot bot commented Sep 9, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🔗 Helpful Links

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

❌ 7 New Failures, 2 Cancelled Jobs, 51 Pending

Uh oh!

Uh oh!

tinglvv commented Sep 9, 2025

Uh oh!

atalman commented Sep 9, 2025

Uh oh!

tinglvv commented Sep 10, 2025

Uh oh!

tinglvv commented Sep 10, 2025

Uh oh!

pytorchmergebot commented Sep 10, 2025

Uh oh!

pytorchmergebot commented Sep 10, 2025

Uh oh!

atalman commented Sep 11, 2025

Uh oh!

pytorchmergebot commented Sep 11, 2025

Merge started

Uh oh!

atalman commented Sep 23, 2025

Uh oh!

pytorchbot commented Sep 23, 2025

Cherry picking #162455

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

tinglvv commented Sep 9, 2025 •

edited

Loading

pytorch-bot bot commented Sep 9, 2025 •

edited

Loading