NXP backend: Fix unittest-nxp-neutron introduced in 0012ffaf9

[robert-kalmar]

Summary

Test plan

pytest -c /dev/null backends/nxp/tests/

cc @digantdesai @JakeStevens

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

✅ You can merge normally! (2 Unrelated Failures)

As of commit 744631a with merge base 373be8c ():

FLAKY - The following jobs failed but were likely due to flakiness present on trunk:

• pull / test-llama_runner_eager-linux / linux-job (gh) (detected as infra flaky with no log or failing log classifier)
• pull / test-llava-runner-linux / linux-job (gh) (detected as infra flaky with no log or failing log classifier)

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.

[JakeStevens]

not sure how this file was missed, should be better going forward with moving the nxp tests

[robert-kalmar]

not sure how this file was missed, should be better going forward with moving the nxp tests

You mean moving from trunk to pull? That is already in place, and the error get triggered on the respective PR #12546. But merged despite that.