🔗 Helpful Links

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

• 📄 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 Merge Blocking SEVs

There is 1 active merge blocking SEVs. Please view them below:

• (merge blocking) Issue with internal merge, blocking merges until further notice

If you must merge, use @pytorchbot merge -f.

❌ 1 Failures

As of commit ad96097:

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

@pytorchbot rebase

@pytorchbot successfully started a rebase job. Check the current status here

Rebase failed due to Command git -C /home/runner/work/pytorch/pytorch rebase refs/remotes/origin/viable/strict gh/desertfire/80/orig returned non-zero exit code 1

Rebasing (1/1)
Auto-merging benchmarks/dynamo/common.py
Auto-merging torch/_inductor/__init__.py
CONFLICT (content): Merge conflict in torch/_inductor/__init__.py
Auto-merging torch/_inductor/codecache.py
Auto-merging torch/_inductor/codegen/cpp.py
Auto-merging torch/_inductor/config.py
CONFLICT (content): Merge conflict in torch/_inductor/config.py
Auto-merging torch/_inductor/graph.py
error: could not apply 1a33bf86067... [reland][inductor] Add an AOT compilation mode for Inductor CPP backend
hint: Resolve all conflicts manually, mark them as resolved with
hint: "git add/rm <conflicted_files>", then run "git rebase --continue".
hint: You can instead skip this commit: run "git rebase --skip".
hint: To abort and get back to the state before "git rebase", run "git rebase --abort".
Could not apply 1a33bf86067... [reland][inductor] Add an AOT compilation mode for Inductor CPP backend

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

@pytorchbot rebase

@pytorchbot successfully started a rebase job. Check the current status here

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

@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 mandatory check(s) failed. The first few are:

• pull / linux-focal-py3.9-clang7-asan / test (default, 2, 5, linux.4xlarge)

Dig deeper by viewing the failures on hud

@pytorchbot merge -f "macos test is flaky"

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes).

Learn more about merging in the wiki.

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

@pytorchbot revert -m 'Sorry for reverting this. It increased the test time significantly for ASAN (and may be other test shards). ASAN tests on PR passed but it was barely not timing out. I have updated my initial findings in #96378' -c weird

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

@desertfire your PR has been successfully reverted.

Please note, that it also added about 2h of test time to MacOS x86 shards and about 30 min of test time to MacOS M1. Does this change really need such exhaustive testing?

I think it only affected CPU tests. Let me look into it.