🔗 Helpful Links

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

• 📄 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 or our office hours

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

✅ You can merge normally! (4 Unrelated Failures)

As of commit e9d7afa with merge base 18785c1 ():

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

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Merge failed

Reason: 2 jobs have failed, first few of them are: trunk / linux-focal-rocm6.2-py3.10 / test (default, 1, 2, linux.rocm.gpu), trunk / linux-focal-rocm6.2-py3.10 / test (distributed, 1, 1, linux.rocm.gpu)

@pytorchbot rebase -b main

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

Rebase failed due to

Aborting rebase because rebasing the branch resulted in the same sha as the target branch.
This usually happens because the PR has already been merged.  Please rebase locally and push.

Raised by https://github.com/pytorch/pytorch/actions/runs/12287295645

@pytorchbot rebase -b main

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

Rebase failed due to

Aborting rebase because rebasing the branch resulted in the same sha as the target branch.
This usually happens because the PR has already been merged.  Please rebase locally and push.

Raised by https://github.com/pytorch/pytorch/actions/runs/12288860276

@pytorchbot merge

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

@cyyever, @clee2000 @albanD

A rebase isn't going to work, because the commit is already contained in main! The rebase process sees the identical commit, just removes it, and then the revert comes after that, and we're back where we started. 😁

The solution I used was to go to the desired commit ID - I picked main - and then use git cherry-pick to textually apply the commit again.

If upstream is the pytorch/pytorch repo, these commands would do it:

git fetch upstream main
git reset --hard upstream/main
git cherry-pick upstream/gh/rec/45/head
ghstack

I did something like this, and it's cooking right now.

Fine , merge it!