🔗 Helpful Links

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

• 📄 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.

❗ 1 Active SEVs

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

• Large queue time for macos-m2-15 instances

❌ 1 Cancelled Job

As of commit 6b1fa20 with merge base a4459cd ():

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

@pytorchbot rebase -b viable/strict

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

Tried to rebase and push PR #153405, but it was already up to date. Try rebasing against main by issuing:
@pytorchbot rebase -b main

@pytorchbot rebase -b main

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

Successfully rebased gh/henrylhtsang/80/orig onto refs/remotes/origin/main, please pull locally before adding more changes (for example, via ghstack checkout https://github.com/pytorch/pytorch/pull/153405)

@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

Merge failed

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

@pytorchbot merge -i

Merge started

Your change will be merged while ignoring the following 1 checks: trunk / linux-jammy-rocm-py3.10 / test (distributed, 1, 1, linux.rocm.gpu.4)

Learn more about merging in the wiki.

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