Qualcomm AI Engine Direct - Optimize UT execution time re-submit

[chenweng-quic]

Summary

• Currently all tests will push same libs, which is redundant. With this PR it only push once, and reduce execution time from two to three times for operator's tests.

Test plan

python backends/qualcomm/tests/test_qnn_delegate.py -k TestQNNFloatingPointOperator --device <device> --host <host> --model SM8650 --build_folder build-android --executorch_root . --artifact all_artifact

without optimization

with optimization

cc @cccclai @cbilgin

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 3 New Failures

As of commit c922887 with merge base 2a570e0 ():

NEW FAILURES - The following jobs have failed:

• Lint / android-java-format / linux-job (gh)
  RuntimeError: Command docker exec -t 4d5b0e091e9308a8b37f6d938a7be856d07b22396a5b38e092013001d5e1c485 /exec failed with exit code 1
• pull / android / build-llm-demo / linux-job (gh)
  RuntimeError: Command docker exec -t 81743c4fca4b28e807092b6c669fcb4fa386f97b4051d270e5cae355aaff546c /exec failed with exit code 1
• pull / unittest-editable / macos / macos-job (gh)
  export/tests/test_target_recipes.py::TestTargetRecipes::test_linear_model

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.

[mergennachin]

@lucylq

Can you import internally and see if it fixed the internal CI tests.

Last week, @GregoryComer reverted (#17014) due to internal CI failures

[mergennachin]

@GregoryComer when reverting, it would be good to provide more information about what the error was in internal CI tests. We can't share everything but providing something would be good than nothing.

[cccclai]

can you rebase to main?

[meta-codesync]

@cccclai has imported this pull request. If you are a Meta employee, you can view this in D92060877.

[cccclai]

I don't see the internal CI failure and will try to merge again. @GregoryComer feel free to chime in