Arm backend: Use default run_on_fvp=True unless explicitly set to False

[SaoirseARM]

Summary

Updates the unit test to use the default run_on_fvp unless explicitly set otherwise.

cc @digantdesai @freddan80 @per @zingo @oscarandersson8218

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 6 New Failures, 7 Unrelated Failures

As of commit dad4f06 with merge base 25b3d63 ():

NEW FAILURES - The following jobs have failed:

• pull / test-qnn-wheel-packages-linux (3.10) / linux-job (gh)
  RuntimeError: Command docker exec -t 509e721ff3fb7c4952655bd11938fede9a286ac31027ab3e2ed92d5f7f429075 /exec failed with exit code 1
• pull / test-qnn-wheel-packages-linux (3.11) / linux-job (gh)
  RuntimeError: Command docker exec -t 8a42ffc51b7bb4b0800f8173eb8629683d7d2a217f9f329c016e2a602d3c3032 /exec failed with exit code 1
• pull / test-qnn-wheel-packages-linux (3.12) / linux-job (gh)
  RuntimeError: Command docker exec -t 0c25945aafa06eb777d6598beef3ce76108d55031539de23d16447dfe50e2eb5 /exec failed with exit code 1
• pull / test-samsung-models-linux / linux-job (gh)
  RuntimeError: Command docker exec -t c488e6d4c13743a06bd3e1693ba6ce34c0dd84494e6e87db58c64c178a90ffcb /exec failed with exit code 1
• pull / unittest / macos / macos-job (gh)
  exir/tests/test_quant_fusion_pass.py::TestQuantFusionPass::test_embedding_torchao
• pull / unittest-editable / macos / macos-job (gh)
  exir/tests/test_quant_fusion_pass.py::TestQuantFusionPass::test_embedding_torchao

FLAKY - The following jobs failed but were likely due to flakiness present on trunk:

• trunk / test-models-linux-aarch64 (w2l, portable, linux.arm64.2xlarge) / linux-job (gh) (detected as infra flaky with no log or failing log classifier)
• trunk / test-models-windows (emformer_transcribe, portable) / windows-job (gh) (detected as infra flaky with no log or failing log classifier)
• trunk / test-models-windows (mobilebert, xnnpack-q8) / windows-job (gh) (detected as infra flaky with no log or failing log classifier)
• trunk / test-models-windows (mv3, portable) / windows-job (gh) (detected as infra flaky with no log or failing log classifier)
• trunk / test-models-windows (mv3, xnnpack-q8) / windows-job (gh) (detected as infra flaky with no log or failing log classifier)

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

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

• pull / test-binary-size-linux-gcc / linux-job (gh) (trunk failure)
  ##[error]The operation was canceled.
• pull / test-setup-linux-gcc / linux-job (gh) (trunk failure)

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

[SaoirseARM]

@pytorchbot label ciflow/trunk

[SaoirseARM]

@pytorchbot label 'partner: arm'

[SaoirseARM]

@pytorchbot label "release notes: none"

[digantdesai]

wouldn't these fail for no-fvp jobs without the xfails?

[digantdesai]

Thanks!

[facebook-github-bot]

@digantdesai has imported this pull request. If you are a Meta employee, you can view this in D83260806.

[digantdesai]

Let me make sure we are not running into some random issue with internal FVP setup with this..

[zingo]

@digantdesai Thanks, did the internal test work OK ?

[digantdesai]

Slice tests like these test_slice_tensor_u55_INT are failing rest are OK. Let me take a look.

[digantdesai]

We use bundled_io for some internal testing, and seems like None in the test_suite for Slice is causing a problem when creating bundled_io. Still digging..

[digantdesai]

I have a fwd fix. I can land this.. thanks for the patience.