Address eellison's CR comments on AOTAutograd

[ezyang]

Stack from ghstack (oldest at bottom):

• -> Address eellison's CR comments on AOTAutograd #85370

For some reason, this change didn't actually make it to master.

Signed-off-by: Edward Z. Yang <ezyangfb.com>

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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 our office hours

Note: Links to docs will display an error until the docs builds have been completed.

❌ 6 Failures

As of commit a72be5c:

The following jobs have failed:

• linux-bionic-cuda11.3-py3.7-clang9 / build
• linux-bionic-cuda11.6-py3.10-gcc7-bazel-test / build-and-test
• linux-focal-py3.7-clang7-asan / build
• linux-focal-py3.7-gcc7-no-ops / build
• linux-jammy-cuda11.6-cudnn8-py3.8-clang12 / build
• linux-xenial-py3-clang5-mobile-custom-build-static / build

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

[ezyang]

@pytorchbot merge

[pytorchmergebot]

@pytorchbot successfully started a merge job. Check the current status here.
The merge job was triggered without a flag. This means that your change will be merged once all checks on your PR have passed (ETA: 0-4 Hours). If this is not the intended behavior, feel free to use some of the other merge options in the wiki.
Please reach out to the PyTorch DevX Team with feedback or questions!

[pytorchmergebot]

Merge failed

Reason: The following mandatory check(s) failed (Rule superuser):

• pull

Dig deeper by viewing the failures on hud

Details for Dev Infra team

Raised by workflow job

[ezyang]

@pytorchbot merge -f "ci flakiness"

[pytorchmergebot]

@pytorchbot successfully started a merge job. Check the current status here.
The merge job was triggered with the force (-f) flag. This means your change will be merged immediately, bypassing any CI checks (ETA: 1-5 minutes). If this is not the intended behavior, feel free to use some of the other merge options in the wiki.
Please reach out to the PyTorch DevX Team with feedback or questions!

[github-actions]

Hey @ezyang.
You've committed this PR, but it does not have both a 'release notes: ...' and 'topics: ...' label. Please add one of each to the PR. The 'release notes: ...' label should represent the part of PyTorch that this PR changes (fx, autograd, distributed, etc) and the 'topics: ...' label should represent the kind of PR it is (not user facing, new feature, bug fix, perf improvement, etc). The list of valid labels can be found here for the 'release notes: ...' and here for the 'topics: ...'.
For changes that are 'topic: not user facing' there is no need for a release notes label.