Qualcomm AI Engine Direct - Debugger Converge Phase 1: Introduce debug handle

[winskuo-quic]

Summary

We will be replacing part of the features in Qualcomm Intermediate Debugger with ExecuTorch's Debugger shortly.
This includes using Intermediate_Output_Capturer to capture CPU golden output and calculate_numeric_gap to perform tensor to tensor comparison.
To reuse these features, one key component is to enable debug_handle since ExecuTorch's tool saves per tensor result with mapping of {debug_handle : tensor_value}

This PR will be the 1st stage of debugger convergence, which is to enable debug_handle.

Test plan

python -m unittest executorch.backends.qualcomm.tests.test_passes.TestPasses.test_resolve_debug_handle

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 1 Awaiting Approval, 3 New Failures

As of commit 7a91e7c with merge base f40bc56 ():

AWAITING APPROVAL - The following workflow needs approval before CI can run:

• periodic (gh)

NEW FAILURES - The following jobs have failed:

• pull / test-samsung-models-linux / linux-job (gh)
  RuntimeError: Command docker exec -t 5d214d5b70254ef46ca143f7d9ae00ab3e0da3724b3b3f41b43af39b64f53ce8 /exec failed with exit code 1
• pull / test-samsung-quantmodels-linux / linux-job (gh)
  RuntimeError: Command docker exec -t a3dfea56b17506532aa1ab5cb3072846d5c13e86f45ecd3063d378d425f34a11 /exec failed with exit code 1
• pull / unittest-arm-backend-with-no-deps (test_pytest_ops_tosa) / linux-job (gh)
  RuntimeError: Command docker exec -t 56e72a703156ad096b9afcdf8a686657b8e7f321370f377c13b1df5c2f2abd09 /exec failed with exit code 1

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.

[winskuo-quic]

Hi @Gasoonjia, @cccclai,
As discussed offline and in the email thread, we will start converging Qualcomm Intermediate Debugger with ExecuTorch's Debugger API.
We will break this feature down 2 to 3 PRs. This will be the first PR, focusing on enabling debug_handle for Qualcomm backend. I have added a unit test to ensure that the behavior is desired.
Please have a look. Thanks