[executorch][qnn] Fix pass migration CI failures

[JacobSzwejbka]

Authored with Codex.

cc @cbilgin @psiddh

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 1 New Failure, 6 Unrelated Failures

As of commit d11bc7a with merge base 89e6f90 ():

NEW FAILURE - The following job has failed:

• Build Presets / windows (pybind) / build (gh)

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

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

• pull / unittest / linux / linux-job (gh) (trunk failure)
  .ci/scripts/tests/test_filter_cuda_matrix.py::TestPublishedSets::test_published_python_versions
• pull / unittest / macos / macos-job (gh) (trunk failure)
  .ci/scripts/tests/test_filter_cuda_matrix.py::TestPublishedSets::test_published_python_versions
• pull / unittest / windows / windows-job (gh) (trunk failure)
  .ci/scripts/tests/test_filter_cuda_matrix.py::TestPublishedSets::test_published_python_versions
• pull / unittest-editable / linux / linux-job (gh) (trunk failure)
  .ci/scripts/tests/test_filter_cuda_matrix.py::TestPublishedSets::test_published_python_versions
• pull / unittest-editable / macos / macos-job (gh) (trunk failure)
  .ci/scripts/tests/test_filter_cuda_matrix.py::TestPublishedSets::test_published_python_versions
• pull / unittest-editable / windows / windows-job (gh) (trunk failure)
  .ci/scripts/tests/test_filter_cuda_matrix.py::TestPublishedSets::test_published_python_versions

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.

[qti-horodnic]

@JacobSzwejbka
Can we add some details to the description? What are the failures, how these changes fix them etc.?

[psiddh]

@JacobSzwejbka Can we add some details to the description? What are the failures, how these changes fix them etc.?

@qti-horodnic I have this follow up PR : #22022? It should have some context