Arm backend: Enable mypy lintrunner for backends/arm/test

[perheld]

Enable the lintrunner to run mypy on backends/arm/test that was ignored in the initial commit of enabling mypy for backends/arm.

Mostly sad ignores but also some actual fixes.

Change-Id: Iba12558511ae938864086eb0539063a87177c0ae

cc @digantdesai @freddan80 @per @zingo @oscarandersson8218

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 1 New Failure, 1 Cancelled Job

As of commit 530e6d1 with merge base 5a5fab7 ():

NEW FAILURE - The following job has failed:

• Lint / lintrunner / linux-job (gh)
  >>> Lint for backends/arm/test/tester/test_pipeline.py:

CANCELLED JOB - The following job was cancelled. Please retry:

• trunk / test-llama-runner-mac (fp32, mps) / macos-job (gh)
  ##[error]The operation was canceled.

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

[perheld]

Well that exploded. I need to investigate why the result differs from our internal CI.

[digantdesai]

wow you made linter really mad!

[byjlw]

Well that exploded. I need to investigate why the result differs from our internal CI.

Any update on this?

[perheld]

Well that exploded. I need to investigate why the result differs from our internal CI.

Any update on this?

Sadly no. Other prios, sick kids and some leave has left this very unattended from me. But I havent forgotten about it.

[perheld]

I've identified why this got through and exploded. In our internal lintrunner we run with --revision HEAD^ and not --all-files so everything was green on our end. I have to run it manually with --all-files and fix all the issues and repush.

Possible with the commit adressing all issues before the commit that enables the checking of this subdirectory. 🫠

[github-actions]

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.

[digantdesai]

❤️

[perheld]

Abandoning this, splitting up to commits per subdirectory for a managed way of getting this done. Starting with #15354