You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Updates NIGHTLY_VERSION in torch_pin.py to dev20260607
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.
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:
This comment was automatically generated by Dr. CI and updates every 15 minutes.
meta-claBot
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 8, 2026
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"
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.
Use your CI tools to download the failure logs for the non-flaky failing jobs
Identify the root cause of the failure
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
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
Run lintrunner -a on any files you change
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
Impact: All jobs running quantization via convert_pt2e() fail — this includes xnnpack-quantization-delegation tests, test_target_recipes, QNN tests, and llama runner tests.
Root cause: PyTorch nightly dev20260607 removed the aten.transpose.Dimname overload from native_functions.yaml. The torchao package (installed as a dependency of torch) still references this overload in port_metadata_pass.py. This is a torchao bug that needs to be fixed upstream in pytorch/ao.
Error:Clang-16 or newer is required to compile PyTorch, but found 12.0.1
Impact: All Docker image builds fail because PyTorch nightly now requires Clang 16+ to compile.
Root cause: The ExecuTorch CI Docker images ship with Clang 12, but PyTorch's new CMakeLists.txt now enforces a minimum of Clang 16.
Conclusion
Neither issue can be fixed by modifying ExecuTorch code:
The Dimname error is inside torchao — a third-party package installed from pip as a transitive dependency of torch. ExecuTorch doesn't control this code. The fix needs to happen in pytorch/ao.
The Clang version requirement is a PyTorch build infrastructure change that requires updating the Docker base images (Clang 12 → Clang 16+), which is a CI infra change, not a code change.
This is a major BC-breaking change that requires coordination with the PyTorch and torchao teams. The PyTorch nightly has broken compatibility with its own ecosystem (torchao), and additionally now requires Clang 16+ which the current CI infrastructure doesn't provide.
Recommended actions:
Wait for pytorch/ao to land a fix for the Dimname overload removal
Update Docker images to use Clang 16+ (separate infra PR)
Re-run the pin bump after both issues are resolved upstream
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
meta-cla
Bot
added
the
CLA Signed
Summary
Automated weekly PyTorch pin bump.
NIGHTLY_VERSIONintorch_pin.pytodev20260607.ci/docker/ci_commit_pins/pytorch.txtto the corresponding nightly commit hashruntime/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