Skip to content

Bump PyTorch pin to nightly dev20260621#20419

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

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

Conversation

@pytorchupdatebot

@pytorchupdatebot pytorchupdatebot commented Jun 22, 2026

Copy link
Copy Markdown
Collaborator

Summary

Automated weekly PyTorch pin bump.

  • Updates NIGHTLY_VERSION in torch_pin.py to dev20260621
  • 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 Jun 22, 2026
@pytorch-bot

pytorch-bot Bot commented Jun 22, 2026 •
edited
Loading

Copy link
Copy Markdown

🔗 Helpful Links

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

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

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

❌ 56 New Failures, 134 Cancelled Jobs, 1 Pending, 1 Unrelated Failure, 14 Unclassified Failures

As of commit 24fbddc with merge base 484f72c (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:

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.

@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 Jun 22, 2026
@github-actions

github-actions Bot commented Jun 22, 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 Jun 22, 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/27947616715

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 Jun 22, 2026 •
edited
Loading

Copy link
Copy Markdown

Claude finished @pytorchupdatebot's task in 8m 17s —— View job

CI fix attempt 1/3 — Root cause found, but fix is outside ExecuTorch code

  • Review Dr. CI summary & identify non-flaky failures
  • Download failure logs
  • Identify root cause
  • Determine whether the fix belongs in ExecuTorch code
  • Fix ExecuTorch code — not applicable (see below)

Root cause

Every non-flaky pull / trunk failure (test-models-* with xnnpack-quantization-delegation, test_w2l_model, etc.) has the same root cause:

File ".../site-packages/torchao/quantization/pt2e/quantizer/port_metadata_pass.py", line 181,
    in _port_metadata_for_input_quant_nodes
    torch.ops.aten.transpose.Dimname,
File ".../torch/_ops.py", line 1243, in __getattr__
AttributeError: The underlying op of 'aten.transpose' has no overload name 'Dimname'

The new PyTorch nightly (dev20260621) removed the Dimname (named-tensor) overload of aten.transpose. The reference to torch.ops.aten.transpose.Dimname lives in torchao (port_metadata_pass.py), which is installed from the third-party/ao submodule (pinned at 02105d46). It is triggered during convert_pt2e for every quantized-delegation export path.

I grepped the ExecuTorch tree — it does not vendor port_metadata_pass.py or reference transpose.Dimname anywhere. The only ExecuTorch use of transpose is torch.ops.aten.transpose.int, which is unaffected. So there is no ExecuTorch source change that fixes this.

Why I'm stopping rather than pushing a fix

Per the task constraints, I'm only to modify ExecuTorch code (not torch_pin.py, the c10 headers, or the pin). This failure is in a third-party dependency (torchao), and the correct fix is one of:

  1. Bump the third-party/ao submodule to a torchao commit where port_metadata_pass.py no longer references the removed aten.transpose.Dimname overload, or
  2. Land the corresponding torchao-side fix upstream first, then bump the submodule pin here.

A submodule bump is coupled to this pin bump but is a separate dependency decision, and I could not verify the correct target torchao commit from this environment (network/gh/curl and submodule checkout are unavailable in the sandbox, so I can't confirm which upstream pytorch/ao commit drops the Dimname reference).

This needs a torchao submodule bump (or an upstream torchao fix) to land alongside the PyTorch pin — it is not fixable by editing ExecuTorch code. Recommend human review (cc @jakeszwe / @pytorchbot).

Other failures (not new / not actionable here)

  • docker-build (*) and Build Aarch64 Linux Wheels (CoreML InMemoryNode::Kind C++ error) are unclassified — they did not run on the merge base, so Dr. CI can't attribute them; they are unrelated to the transpose.Dimname regression.
  • The linter docker-build and linux-arm64 flaky entry (registry-1.docker.io head error) are infra/flaky.
    · branch automated/pytorch-pin-bump-dev20260621

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