Arm backend: Output pytest report in trunk jobs

[Erik-Lundell]

When a pytest report is output to $RUNNER_TEST_RESULTS_DIR, the linux_job_v2.yml workflow can pick it up and
surface it in github ci.

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/19555

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

• Run pull request jobs on OSDC runners in shadow mode

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

As of commit 448c268 with merge base f1062a7 ():

NEW FAILURES - The following jobs have failed:

• pull / test-qnn-passes-linux / linux-job (gh)
  RuntimeError: Command docker exec -t 6615dffa3b089b3bd59037ebe0c1f7b381920319734a0d55f3ffbe4f25621796 /exec failed with exit code 1
• pull / unittest-editable / macos / macos-job (gh)
  exir/tests/test_memory_planning.py::TestMisc::test_multiple_pools_1
• trunk / unittest-release / macos / macos-job (gh)
  export/tests/test_target_recipes.py::TestTargetRecipes::test_linear_model

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

• trunk / test-custom-ops-macos (cmake) / macos-job (gh)
  ##[error]The operation was canceled.

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

• trunk / unittest-release / linux / linux-job (gh) (similar failure)
  exir/tests/test_joint_graph.py::TestJointGraph::test_joint_graph

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)
  exir/tests/test_joint_graph.py::TestJointGraph::test_joint_graph
• pull / unittest / macos / macos-job (gh) (trunk failure)
  exir/tests/test_joint_graph.py::TestJointGraph::test_joint_graph
• pull / unittest / windows / windows-job (gh) (trunk failure)
  exir/tests/test_joint_graph.py::TestJointGraph::test_joint_graph
• pull / unittest-editable / linux / linux-job (gh) (trunk failure)
  exir/tests/test_joint_graph.py::TestJointGraph::test_joint_graph
• pull / unittest-editable / windows / windows-job (gh) (trunk failure)
  exir/tests/test_joint_graph.py::TestJointGraph::test_joint_graph
• trunk / unittest-release / windows / windows-job (gh) (trunk failure)
  exir/tests/test_joint_graph.py::TestJointGraph::test_joint_graph

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.