Enable mypy check in torch/_inductor/fx_passes/post_grad.py

[FFFrog]

Fixes #105230

$ lintrunner init && lintrunner -a torch/_inductor/fx_passes/post_grad.py
...
ok No lint issues.
Successfully applied all patches.

$ mypy torch/_inductor/fx_passes/post_grad.py
Success: no issues found in 1 source file


cc @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @Xia-Weiwen @wenzhe-nrv @jiayisunx @peterbell10 @ipiszy @ngimel @yf225 @chenyang78 @kadeng @muchulee8 @aakhundov

[pytorch-bot]

🔗 Helpful Links

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

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

• Long ROCm queue (2023-08-18)

✅ 1 Unrelated Failure

As of commit 697549c with merge base c21e9de ():

BROKEN TRUNK - The following job failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

• linux-jammy-py3.9-clang12-asan / test (default, 1, 6, linux.4xlarge) (gh)

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

[FFFrog]

@pytorchbot label "topic: not user facing"

[ezyang]

@pytorchbot merge -r main

[pytorchmergebot]

@pytorchbot started a rebase job onto refs/remotes/origin/main. Check the current status here

[pytorchmergebot]

Successfully rebased mrl_fix_post_grad onto refs/remotes/origin/main, please pull locally before adding more changes (for example, via git checkout mrl_fix_post_grad && git pull --rebase)

[pytorchmergebot]

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

Advanced Debugging

Check the merge workflow status
here

[pytorchmergebot]

The merge job was canceled. If you believe this is a mistake,then you can re trigger it through pytorch-bot.

[ezyang]

@pytorchbot merge -f "bypass rocm"

[pytorchmergebot]

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

Advanced Debugging

Check the merge workflow status
here