Skip to content

Bump PyTorch pin to nightly dev20260726 - #21394

Open
pytorchupdatebot wants to merge 1 commit into
mainfrom
automated/pytorch-pin-bump-dev20260726
Open

Bump PyTorch pin to nightly dev20260726#21394
pytorchupdatebot wants to merge 1 commit into
mainfrom
automated/pytorch-pin-bump-dev20260726

Conversation

@pytorchupdatebot

@pytorchupdatebot pytorchupdatebot commented Jul 27, 2026

Copy link
Copy Markdown
Collaborator

Summary

Automated weekly PyTorch pin bump.

  • Updates NIGHTLY_VERSION in torch_pin.py to dev20260726
  • Updates .ci/docker/ci_commit_pins/pytorch.txt to the corresponding nightly commit hash
  • Syncs c10 headers from PyTorch into runtime/core/portable_type/c10/

This PR was created automatically. If CI fails, Claude will attempt to fix issues (up to 3 attempts). If CI still fails, human review will be requested.

cc @jakeszwe

@pytorch-bot pytorch-bot Bot added the ci-no-td label Jul 27, 2026
@pytorch-bot

pytorch-bot Bot commented Jul 27, 2026 •
edited
Loading

Copy link
Copy Markdown

🔗 Helpful Links

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

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

❌ 52 New Failures, 187 Cancelled Jobs, 26 Unclassified Failures

As of commit a669ae8 with merge base 3aeaa80 (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 27, 2026
@github-actions

github-actions Bot commented Jul 27, 2026

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.

@pytorchupdatebot

pytorchupdatebot commented Jul 27, 2026

Copy link
Copy Markdown
Collaborator Author

@claude [ci-fix-attempt 1/3]

The trunk CI workflow has failed on this automated PyTorch pin bump PR.
Failed run: https://github.com/pytorch/executorch/actions/runs/30257606829

Please:

  1. Read the Dr. CI comment on this PR for a summary of which jobs failed and whether they are flaky. Ignore failures marked as FLAKY.
  2. Use your CI tools to download the failure logs for the non-flaky failing jobs
  3. Identify the root cause of the failure
  4. If this is a build or test failure caused by PyTorch API changes, fix the ExecuTorch code to be compatible with the new PyTorch version
  5. If this is a c10 header sync issue, the headers have already been synced by the pin bump script — the issue is likely in ExecuTorch code that uses those headers
  6. Run lintrunner -a on any files you change
  7. Push your fix as a new commit to this PR branch

Important constraints:

  • Do NOT modify torch_pin.py or .ci/docker/ci_commit_pins/pytorch.txt — the pin itself is correct
  • Do NOT modify files under runtime/core/portable_type/c10/ unless the sync introduced a new API that ExecuTorch code needs to adapt to
  • Focus on fixing ExecuTorch code to be compatible with the new PyTorch APIs
  • If this is a major BC-breaking change that requires architectural discussion, say so clearly and stop — do not attempt a fix

@claude

claude Bot commented Jul 27, 2026 •
edited
Loading

Copy link
Copy Markdown

Claude finished @pytorchupdatebot's task in 6m 41s —— View job

CI Fix — PyTorch pin bump (attempt 1/3)

Root cause identified. PyTorch nightly dev20260726 (torch 2.14) removed python setup.py bdist_wheel as a build entrypoint — it now hard-errors (pytorch#152276):

error: `python setup.py bdist_wheel` is deprecated: PyTorch is built with
scikit-build-core via the standard PEP 517 interface (pyproject.toml),
and setup.py is no longer part of the build.

Two ExecuTorch scripts build PyTorch from source this way, which accounts for essentially all the non-flaky failures:

  • Linux docker-build jobs → .ci/docker/common/install_pytorch.sh:53 fails → cascades into every "Calculate docker image" failure across pull/trunk (the docker image can't be built, so all downstream Linux jobs are blocked).
  • macOS unittest* jobs → the cached nightly wheel 404s, so it falls back to the source build in .ci/scripts/utils.sh:138 and fails.

Fix applied (committed locally): swap the removed entrypoint for the PyTorch-documented replacement python -m build --wheel --no-isolation, and install the build package (not in requirements-build.txt). Env-var customization (USE_DISTRIBUTED, MAX_JOBS, …) works unchanged per PyTorch's deprecation notice, and python -m build --wheel emits an identically-named wheel in dist/, so the macOS cache-key invariant still holds.

--- a/.ci/docker/common/install_pytorch.sh
+++ b/.ci/docker/common/install_pytorch.sh
   configure_pytorch_compiler
-  # Then build and install PyTorch
-  conda_run python setup.py bdist_wheel
+  # Then build and install PyTorch. `python setup.py bdist_wheel` was removed as
+  # a build entrypoint in torch 2.14; use the PEP 517 replacement instead.
+  pip_install build
+  conda_run python -m build --wheel --no-isolation
   pip_install "$(echo dist/*.whl)"

--- a/.ci/scripts/utils.sh
+++ b/.ci/scripts/utils.sh
-    pip install -r requirements-build.txt
+    pip install -r requirements-build.txt build
     ...
-    USE_DISTRIBUTED=1 python setup.py bdist_wheel
+    # `python setup.py bdist_wheel` was removed as a build entrypoint in torch
+    # 2.14; use the PEP 517 replacement instead.
+    USE_DISTRIBUTED=1 python -m build --wheel --no-isolation
  • Read Dr. CI summary & identify non-flaky failures
  • Download failure logs for real failures
  • Identify root cause
  • Fix .ci/docker/common/install_pytorch.sh
  • Fix .ci/scripts/utils.sh
  • Run lintrunner -a — ⚠️ blocked (see below)
  • Push fix — ⚠️ blocked (see below)

⚠️ Unable to push

The push was rejected by a branch ruleset:

remote: error: GH013: Repository rule violations found ...
remote: - Required status check "Meta CLA Check" is expected.

This is a push-time required-status-check rule on the branch, not an authorship problem (re-authoring the commit as claude[bot] didn't change it). I don't have a way to bypass it from this environment. lintrunner invocation was also declined by the sandbox, though these are trivial shell edits (one-line command swap + pip install build) that shellcheck won't flag.

The fix above is complete and ready — a maintainer can either apply the two-line diff directly or re-run the push. cc @jakeszwe
· branch automated/pytorch-pin-bump-dev20260726

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

Reviewers

@JacobSzwejbka JacobSzwejbka Awaiting requested review from JacobSzwejbka JacobSzwejbka is a code owner

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

ci/pytorch-pin-bump ci-no-td 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

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@pytorchupdatebot @pytorchbot