Fix QNN simulator runner resolution

[psiddh]

Summary: Materialize qnn_executor_runner as part of the QNN delegate simulator test target and pass its Buck-built path to the Python harness. Prefer that explicit runner path when running x86 simulator tests, while keeping the existing build_folder-based fallback for manual runs.

Differential Revision: D104701942

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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 jobs on OSDC in pull requests shadow mode

❌ 5 New Failures, 1 Unrelated Failure, 1 Unclassified Failure

As of commit eabacf3 with merge base 4d9b0e9 ():

NEW FAILURES - The following jobs have failed:

• pull / unittest / linux / linux-job (gh)
  exir/tests/test_memory_planning.py::TestMisc::test_multiple_pools_1
• pull / unittest / macos / macos-job (gh)
  export/tests/test_target_recipes.py::TestTargetRecipes::test_mv2_model
• pull / unittest-editable / linux / linux-job (gh)
  exir/tests/test_memory_planning.py::TestMisc::test_multiple_pools_1
• pull / unittest-editable / macos / macos-job (gh)
  export/tests/test_target_recipes.py::TestTargetRecipes::test_mv2_model
• pull / unittest-editable / windows / windows-job (gh)
  exir/emit/test/test_emit.py::TestEmit::test_delegate_deduplicate

UNCLASSIFIED FAILURE - DrCI could not classify the following job because the workflow did not run on the merge base. The failure may be pre-existing on trunk or introduced by this PR:

• periodic (gh) (this job did not run on the merge base, so DrCI cannot tell whether the failure is pre-existing)

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

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

• pull / unittest / 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.

[meta-codesync]

@psiddh has exported this pull request. If you are a Meta employee, you can view the originating Diff in D104701942.

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

[Copilot]

Pull request overview

This PR improves how the Qualcomm QNN simulator tests locate and invoke qnn_executor_runner by allowing an explicit runner path to be provided via environment variable, while preserving the existing build-folder-based default.

Changes:

• Read QNN_EXECUTOR_RUNNER from the environment to determine the runner binary path.
• Fall back to ${build_folder}/examples/qualcomm/executor_runner/qnn_executor_runner when the env var is not set.
• Use the resolved runner path when constructing the simulator subprocess command.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[digantdesai]

Review automatically exported from Phabricator review in Meta.