Arm backend: Wrap modules in test_nn_modules

[Erik-Lundell]

This has been observed to mitigate a compilation error when quantizing.

cc @freddan80 @per @zingo @oscarandersson8218 @digantdesai

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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:

• AWS was down, GHA infrastructure effected / recovering

❌ 7 New Failures, 3 Unrelated Failures

As of commit a79f365 with merge base eb05056 ():

NEW FAILURES - The following jobs have failed:

• pull / test-samsung-models-linux / linux-job (gh)
  RuntimeError: Command docker exec -t c9186f8cb9c0d5bb6c9986dc2f432733f5bd0d9ff28f7c42fd62dd137831e34b /exec failed with exit code 1
• pull / unittest / macos / macos-job (gh)
  export/tests/test_target_recipes.py::TestTargetRecipes::test_linear_model
• pull / unittest-nxp-neutron / linux-job (gh)
  RuntimeError: Command docker exec -t ace0d545487d895303f99016690ee3f80cc68510eb3506a8d4ba1f083f15bc97 /exec failed with exit code 1
• Test CUDA Builds / export-voxtral-cuda-non-quantized / linux-job (gh)
  RuntimeError: Command docker exec -t fed53161827f6e3b3f392713e9de50626feb1f4d6ef70c2fb8d265ba4bd2fc09 /exec failed with exit code 2
• Test CUDA Builds / export-voxtral-cuda-quantized-int4-tile-packed / linux-job (gh)
  RuntimeError: Command docker exec -t 23c116fbd26797aaac743ec3bfe06bbbd872102dce3f64cd6d76d2c9192bd145 /exec failed with exit code 2
• Test CUDA Builds / export-voxtral-cuda-quantized-int4-weight-only / linux-job (gh)
  RuntimeError: Command docker exec -t 8b8d367ebe2f2ee0f81381e1f8466a2590a14167b1ac0950f32d5d6a4e5e43f9 /exec failed with exit code 2
• Test Metal Backend / export-voxtral-metal-artifact / macos-job (gh)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 2

FLAKY - The following job failed but was likely due to flakiness present on trunk:

• pull / unittest-editable / linux / linux-job (gh) (matched linux rule in flaky-rules.json)
  The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.

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

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

• pull / unittest / linux / linux-job (gh) (trunk failure)
• trunk / unittest-release / linux / linux-job (gh) (trunk failure)

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