Qualcomm AI Engine Direct - HF LLM E2E Test Refactor

[winskuo-quic]

Summary

A minor refactor on HF LLM model UT, so it is easier to maintain

Test plan

UT pass

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 1 Cancelled Job, 6 Unrelated Failures

As of commit ea5a454 with merge base 993254c ():

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

• Test CoreML Backend / test-coreml / test-backend-macos (coreml_static_int8, operators) / macos-job (gh)
  ##[error]The operation was canceled.

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

• pull / test-openvino-linux / linux-job (gh) (similar failure)
  ##[error]The operation was canceled.

BROKEN TRUNK - The following jobs failed but was present on the merge base:

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

• pull / test-binary-size-linux-gcc / linux-job (gh) (trunk failure)
  ##[error]The operation was canceled.
• pull / test-setup-linux-gcc / linux-job (gh) (trunk failure)
  ##[error]The operation was canceled.
• pull / unittest / windows / windows-job (gh) (trunk failure)
  backends/xnnpack/test/ops/test_conv1d.py::TestConv1d::test_qs8_conv1d_batchnorm_seq
• pull / unittest-editable / windows / windows-job (gh) (trunk failure)
  backends/xnnpack/test/ops/test_conv1d.py::TestConv1d::test_qs8_conv1d_batchnorm_seq
• trunk / unittest-release / windows / windows-job (gh) (trunk failure)
  backends/xnnpack/test/ops/test_conv1d.py::TestConv1d::test_qs8_conv1d_batchnorm_seq

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.

[cccclai]

There are still some failing jobs..

[winskuo-quic]

There are still some failing jobs..

Thanks for reviewing the PR.
I double checked the failed tests, and it seems not directly related to this PR. Could you confirm? Thanks

[cccclai]

Can you rebase? Just would like to double check

[winskuo-quic]

Can you rebase? Just would like to double check

Just rebased. Could you also help trigger the nightly CI? Thanks

[cccclai]

Thanks for making the change!