Skip to content

Bump PyTorch pin to 2.13#20830

Open
JacobSzwejbka wants to merge 1 commit into
mainfrom
js/pytorch-2.13-pin-bump
Open

Bump PyTorch pin to 2.13#20830
JacobSzwejbka wants to merge 1 commit into
mainfrom
js/pytorch-2.13-pin-bump

Conversation

@JacobSzwejbka

@JacobSzwejbka JacobSzwejbka commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

Summary:

  • bump the CI/source PyTorch pin from release/2.12 to release/2.13
  • bump install-time torch from 2.12.0 to 2.13.0 and torchvision from 0.27.0 to 0.28.0
  • sync copied c10 headers with PyTorch release/2.13
  • bump the torchao submodule to include the upstream PyTorch 2.13 aten.transpose.Dimname fix
  • build PyTorch with gcc/g++ inside clang<16 Docker images, since PyTorch 2.13 now requires clang 16+

Notes:

  • torchaudio remains on 2.11.0 / release/2.11 because pytorch/audio does not currently publish a 2.13.0 tag or release/2.13 branch.

Validation:

  • /usr/bin/python3 -m py_compile install_requirements.py torch_pin.py
  • bash -n .ci/docker/common/install_pytorch.sh .ci/scripts/utils.sh
  • .ci/scripts/check_c10_sync.sh
  • checked failed PR logs for the repeated torchao Dimname and clang-12 PyTorch source-build failures

@pytorch-bot

pytorch-bot Bot commented Jul 10, 2026

Copy link
Copy Markdown

🔗 Helpful Links

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

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

❌ 62 New Failures, 173 Cancelled Jobs, 19 Unclassified Failures

As of commit e3ea515 with merge base a588b26 (image):

NEW FAILURES - The following jobs have failed:

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:

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

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

@meta-cla meta-cla Bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Jul 10, 2026
@github-actions

Copy link
Copy Markdown

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant