Arm backend: Add NGP unit test scripts

[mansnils]

Prepare scripts for CI.

cc @digantdesai @freddan80 @per @zingo @oscarandersson8218

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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:

• ROCm MI2xx CI/CD workflows failing due to : download from https://api.github.com/repos/pytorch/pytorch timed out.

❌ 3 New Failures, 1 Cancelled Job, 8 Unrelated Failures

As of commit 33ff8c6 with merge base ebdd12d ():

NEW FAILURES - The following jobs have failed:

• Build documentation / build (buck2) / Build doc (gh)
  At least one of the pre-conditions you specified did not hold
• trunk / test-models-macos-coreml (ic4) / macos-job (gh)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 139
• trunk / test-models-macos-cpu (llama3_2_vision_encoder, portable) / macos-job (gh)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 139

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

• trunk / test-huggingface-transformers-coreml (qwen3-1.7b|xnnpack|--quantize) / macos-job (gh)
  ##[error]The operation was canceled.

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

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

• trunk / test-arm-backend (test_models_ethos-u55) / linux-job (gh) (trunk failure)
  AttributeError: 'bool' object has no attribute 'lower'
• trunk / test-arm-backend (test_models_ethos-u85) / linux-job (gh) (trunk failure)
  AttributeError: 'bool' object has no attribute 'lower'
• trunk / test-arm-backend (test_models_tosa) / linux-job (gh) (trunk failure)
  AttributeError: 'bool' object has no attribute 'lower'
• trunk / test-llama-runner-mac (fp32, coreml) / macos-job (gh) (trunk failure)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 2
• trunk / test-llama-runner-mac (fp32, mps) / macos-job (gh) (trunk failure)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 2
• trunk / test-llama-runner-mac (fp32, xnnpack+custom+quantize_kv) / macos-job (gh) (trunk failure)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 2
• trunk / test-llama-torchao-lowbit / macos-job (gh) (trunk failure)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 2
• trunk / test-mcu-models (cmake) / linux-job (gh) (trunk failure)
  AttributeError: 'bool' object has no attribute 'lower'

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

[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]

this will build and link ET Vulkan backend, ok for now but why do we need this?

[mansnils]

We use the platform and runtime environment provided by the Vulkan delegate

[digantdesai]

Couple of high level questions,
(1) how do you envision evolution of these setup, build, run script with ethos?
(2) why not add the scripts introduced in the PR on the CI? I might be missing something in terms of runtime dependency but I am asking as a way to test these code you are introducing. If not run, let's at least build?

[mansnils]

Couple of high level questions, (1) how do you envision evolution of these setup, build, run script with ethos? (2) why not add the scripts introduced in the PR on the CI? I might be missing something in terms of runtime dependency but I am asking as a way to test these code you are introducing. If not run, let's at least build?

Thanks for your comments.

1. We plan to refactor this, specially the setup part
2. The patch has potential for merge conflicts, in fact one already happened. I think the fastest way is to merge it then enable CI as a second patch

[mansnils]

Ethos-U failures unrelated to this PR