Arm backend: Add a repro command when VGF model-converter fails

[wwwind]

Add a repro command when VGF model-converter fails. This is the fisrt part of the project to create unified bundle in case of failure.

cc @digantdesai @freddan80 @per @zingo @oscarandersson8218 @mansnils @Sebastian-Larsson @robell @rascani

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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] MI350 CI jobs will have longer queue times due to CI migration

❌ 8 New Failures, 6 Pending, 5 Unrelated Failures

As of commit e854017 with merge base e98e74e ():

NEW FAILURES - The following jobs have failed:

• pull / android / run-emulator (gh)
  The process '/usr/local/lib/android/sdk/platform-tools/adb' failed with exit code 224
• pull / test-arm-backend-no-driver (test_pytest_ops_tosa) / linux-job (gh)
  RuntimeError: Command docker exec -t 2ac449939f273f7a9f596a0afa7690515dfbda2c3909579a895908e07fc18d28 /exec failed with exit code 1
• pull / test-qnn-testsuite-linux / test-backend-linux (qnn, operators) / linux-job (gh)
  RuntimeError: Command docker exec -t e910f9135bcb5584600af9d9306c7b7b256f511af20ff68f5bea5e8c4fe6042f /exec failed with exit code 92
• pull / unittest / linux / linux-job (gh)
  RuntimeError: Command docker exec -t e8c2b91c86a33d30c086dc154743f4c99db02e72a511971a8d017b650ac0d25f /exec failed with exit code 1
• pull / unittest-editable / linux / linux-job (gh)
  RuntimeError: Command docker exec -t 34039ba64546f8f55d1cfcf09c3c0e21830f252e530485fe266d9e918a0154a9 /exec failed with exit code 1
• trunk / test-qnn-model (fp32, ic4) / linux-job (gh)
  RuntimeError: Command docker exec -t 43633886a84c9464019775b44394c5f855df4688db366e3be0e843df6ba2bd6a /exec failed with exit code 92
• trunk / test-qnn-optimum-model (fp32, focalnet) / linux-job (gh)
  RuntimeError: Command docker exec -t 6fd4937f2c1f4e0a8b88ce418bb149ac7f9bea611419535cd74adb93e5643085 /exec failed with exit code 92
• trunk / unittest-release / linux / linux-job (gh)
  RuntimeError: Command docker exec -t e57d1eacbee4e1859f91f5ff5630b8e1ef954148a8156edb36672abcdd97120b /exec failed with exit code 1

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

• pull / unittest / macos / macos-job (gh) (similar failure)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 1
• trunk / unittest-release / macos / macos-job (gh) (similar failure)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script 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 / test-llama-runner-qnn-linux (fp32, qnn_16a16w, qnn) / linux-job (gh) (trunk failure)
• pull / unittest-editable / macos / macos-job (gh) (trunk failure)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 1
• trunk / test-llama-runner-qnn-linux (fp32, qnn_16a16w, qnn) / linux-job (gh) (trunk failure)

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

[wwwind]

failures are irrelevant to this PR