Arm backend: Convert ExportPasses to ArmPasses

[martinlsm]

All passes in backends/arm/_passes have been set to inherit from ArmPass instead of ExportPass.

Furthermore, the attribute exported_program in ArmPass has been removed to instead let each subclasses set it. The reason is that it was type annotated as an Optional[ExportedProgram]] in ArmPass and Mypy complained about that when a subclass tried to access it without checking for None. By moving the attribute down to each subclass that needs it, the confusion around whether the value is None or not is elimininated.

Test plan

The persistent tests in the Arm backend should cover this change.

cc @digantdesai @freddan80 @per @zingo @oscarandersson8218

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 7 New Failures, 3 Unrelated Failures

As of commit ca3e577 with merge base 57a7903 ():

NEW FAILURES - The following jobs have failed:

• pull / test-samsung-models-linux / linux-job (gh)
  RuntimeError: Command docker exec -t 4623ed5932d1994c2b33e64e68a9aca327178cc1cda030835c58df919cd44cbb /exec failed with exit code 1
• Test CUDA Builds / export-voxtral-cuda-artifact / linux-job (gh)
  RuntimeError: Command docker exec -t 56822f11c5ac3097657cf191a4114237b106d5ce9cd8e1623046c70adc23bc0a /exec failed with exit code 2
• Test CUDA Builds / test-models-cuda (add_mul) / linux-job (gh)
  RuntimeError: Command docker exec -t 1a002d64cb1abef166d19615af1e3b1f34098bdac25d638bb31ba5369516b7f5 /exec failed with exit code 1
• Test CUDA Builds / test-models-cuda (add) / linux-job (gh)
  RuntimeError: Command docker exec -t 9449d84b66a9dd6e6687713b617de6ecb6fc37acaab6f311f54d74c4900731b4 /exec failed with exit code 1
• Test CUDA Builds / test-models-cuda (conv1d) / linux-job (gh)
  RuntimeError: Command docker exec -t 6e0468e9db42b688007a4202bc279836145bddf0c0e1d10dcf3e094278524204 /exec failed with exit code 1
• Test CUDA Builds / test-models-cuda (linear) / linux-job (gh)
  RuntimeError: Command docker exec -t 0c875b8ee7e94cba903e4ad8b43cb3e37871d0e84c1e0e05c46072b163cd23d7 /exec failed with exit code 1
• Test CUDA Builds / test-models-cuda (resnet18) / linux-job (gh)
  RuntimeError: Command docker exec -t cbb84969d46fd31ea121639b43be10e5832d5a07ea728fbf2a244c5c3f6a08a5 /exec failed with exit code 1

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

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

• pull / unittest / windows / windows-job (gh) (trunk failure)
  runtime/test/test_runtime_etdump_gen.py::RuntimeETDumpGenTest::test_etdump_params_with_bytes_and_buffer
• pull / unittest-editable / windows / windows-job (gh) (trunk failure)
  runtime/test/test_runtime_etdump_gen.py::RuntimeETDumpGenTest::test_etdump_params_with_bytes_and_buffer
• trunk / unittest-release / windows / windows-job (gh) (trunk failure)
  runtime/test/test_runtime_etdump_gen.py::RuntimeETDumpGenTest::test_etdump_params_with_bytes_and_buffer

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

[martinlsm]

@pytorchbot label ciflow/trunk

[martinlsm]

@pytorchbot label "partner: arm"

[github-actions]

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

[digantdesai]

I think this is a step in the right direction.

Just a word of caution for the passes which do use exported_program mainly with an intention to add modes which ends up updating the graph signature i.e. using utils like, create_constant_placeholder is that if the graph inside the exported program and the graph the pass got are out of sync then all sorts of weird errors can happen. So it might be wise to assert something like id(exported_progra.graph_module) == if(pass_arg_graph_module)

[Sebastian-Larsson]

Unrelated CI failures