🔗 Helpful Links

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

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

• Multiple CI trunk failures after landing https://github.com/pytorch/pytorch/pull/161002

⏳ No Failures, 50 Pending

As of commit 574040d with merge base 30384ab ():
💚 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: D80553588

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

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

@pytorchbot merge

(Initiating merge automatically since Phabricator Diff has merged)

Merge failed

Reason: This PR needs a release notes: label
If your changes are user facing and intended to be a part of release notes, please use a label starting with release notes:.

If not, please add the topic: not user facing label.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "topic: not user facing"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

@pytorchbot label "topic: not user facing"

@pytorchbot merge -c ghfirst -f"this is already backed out"

❌ 🤖 pytorchbot command failed:

@pytorchbot: error: unrecognized arguments: -c ghfirst

usage: @pytorchbot [-h] {merge,revert,rebase,label,drci,cherry-pick} ...

Try @pytorchbot --help for more info.

@pytorchbot merge -c ghfirst -f "this is already backed out"

❌ 🤖 pytorchbot command failed:

@pytorchbot: error: unrecognized arguments: -c ghfirst

usage: @pytorchbot [-h] {merge,revert,rebase,label,drci,cherry-pick} ...

Try @pytorchbot --help for more info.

@pytorchbot merge -f "this is already backed out"

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

Merge failed

Reason: Approvers from one of the following sets are needed:

• superuser (pytorch/metamates)
• Core Reviewers (mruberry, lezcano, Skylion007, ngimel, peterbell10, ...)
• Core Maintainers (soumith, gchanan, ezyang, dzhulgakov, malfet, ...)

@pytorchbot merge -f "this is already backed out"

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

This PR is causing failures for both rocm and cuda. See the following link:
https://hud.pytorch.org/failure?name=rocm%20%2F%20linux-jammy-rocm-py3.10%20%2F%20test%20(default%2C%202%2C%206%2C%20linux.rocm.gpu.2)&jobName=undefined&failureCaptures=test_cuda.py%3A%3ATestCudaMallocAsync%3A%3Atest_allocator_settings

@amdfaa I will try to revert #156165 and #156175 which is part of the same stack

@pytorchbot revert -c ghfirst -m "This PR breaks CI TestCudaMallocAsync::test_allocator_settings"

@pytorchbot successfully started a revert job. Check the current status here.
Questions? Feedback? Please reach out to the PyTorch DevX Team

@joshuuuasu your PR has been successfully reverted.

@joshuuuasu @izaitsevfb I will revert this PR first to make the current CI pass. And then I will prepare a PR to help revert the stack of #156175

@joshuuuasu @izaitsevfb I will revert this PR first to make the current CI pass. And then I will prepare a PR to help revert the stack of #156175

@guangyey, thanks! please coordinate the efforts with @atalman in the slack.

@pytorchbot merge -i

(Initiating merge automatically since Phabricator Diff has merged, merging with -i because oss signals were bypassed internally)

Merge started

Your change will be merged while ignoring the following 0 checks:

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: Meta Internal-Only Changes Check