🔗 Helpful Links

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

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

❌ 3 Cancelled Jobs, 8 Pending, 1 Unrelated Failure

As of commit beea6d9 with merge base cdb144f ():

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

@pytorchmergebot merge -i

Merge started

Your change will be merged while ignoring the following 4 checks: docker-builds / docker-build (linux.12xlarge, pytorch-linux-jammy-cuda12.8-cudnn9-py3.9-linter), pull / cuda12.8-py3.10-gcc9-sm75 / test (pr_time_benchmarks, 1, 1, linux.g4dn.metal.nvidia.gpu, unstable), Lint / lintrunner-noclang / linux-job, Lint / lintrunner-clang / linux-job

Learn more about merging in the wiki.

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

@pytorchmergebot merge -f "Images could build"

The merge job was canceled or timed out. This most often happen if two merge requests were issued for the same PR, or if merge job was waiting for more than 6 hours for tests to finish. In later case, please do not hesitate to reissue the merge command
For more information see pytorch-bot wiki.

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

Learn more about merging in the wiki.

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