🔗 Helpful Links

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

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

✅ No Failures

As of commit c777e69 with merge base 8316f9b ():
💚 Looks good so far! There are no failures yet. 💚

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

This pull request was exported from Phabricator. Differential Revision: D62731130

@jeffdaily does the ciflow/rocm label trigger some additional AMD specific CI?

@jeffdaily does the ciflow/rocm label trigger some additional AMD specific CI?

We have a limited pool of CI servers. The ciflow/trunk will trigger a fraction of the full CI suite (no inductor, a select set of test modules, etc). OTOH, ciflow/rocm runs much more. We try to limit using ciflow/rocm on PRs because it puts pressure on our CI resources. We have the authority to revert merged PRs if they break ROCm, in which case we add the ciflow/rocm label to the reverted PR to aid the PR author in fixing the issue for ROCm.

This pull request was exported from Phabricator. Differential Revision: D62731130

@pytorchbot merge -f 'Landed internally'

(Initiating merge automatically since Phabricator Diff has merged, using force because this PR might not pass merge_rules.json but landed internally)

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