lintrunner-noclang job may diverge from `lintrunner` locally about pytorch HOT 4 OPEN

@zou3519 can you run collect env (or at the very least say whether or not you run it on Mac or Linux)

And results are bound to be different if you are using different python version that the one used in CI. Luckily one can run the same container

And last but not least, one should run lintrunner --all, as -a stands for --apply-patches if I'm not mistaken

from pytorch.

collect_env output: https://gist.github.com/zou3519/5b7b877c77810574e67084299291c03e

lintrunner failed in mypy (https://github.com/pytorch/pytorch/actions/runs/8571927570/job/23494053626). I have the same version of mypy locally that lintrunner is using. The difference is that lintrunner in CI is on python 3.9 but I'm on Python 3.11.

So... maybe a mypy thing with different versions of Python

from pytorch.

I'm seeing this again on some more PRs. The interesting thing is running mypy directly does catch issues, but running lintrunner --all-files does not

from pytorch.

I think my problem may have been that when the dmypy daemon hangs, lintrunner erroneously reports mypy as passing. Action item would be to get lintrunner to error out in this situation.

from pytorch.