Update requirements-tests.txt in NXP

[mergennachin]

See if it fixes nxp unit test

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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, 8 Pending, 3 Unrelated Failures

As of commit c9757a1 with merge base e58fdb6 ():

NEW FAILURES - The following jobs have failed:

• pull / test-llava-runner-linux / linux-job (gh)
  RuntimeError: Command docker exec -t 5cea9b8079896750130e940048e81d495123e4268a80ad0730655c711792ab83 /exec failed with exit code 139
• trunk / test-selective-build-macos (cmake) / macos-job (gh)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 1
• trunk / unittest-nxp-neutron / linux-job (gh)
  RuntimeError: Command docker exec -t e1836be938e0ebeec1502ec8cd8879f9ef66ad82f153eea0bfcbbbbfbce46833 /exec failed with exit code 1

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)
  /pytorch/executorch/backends/vulkan/runtime/api/containers/Tensor.cpp:651:17: error: no matching constructor for initialization of 'vkcompute::api::vTensor::TextureLimits'
• pull / unittest-editable / linux / linux-job (gh) (trunk failure)
  /pytorch/executorch/backends/vulkan/runtime/api/containers/Tensor.cpp:651:17: error: no matching constructor for initialization of 'vkcompute::api::vTensor::TextureLimits'
• trunk / unittest-release / linux / linux-job (gh) (trunk failure)
  /pytorch/executorch/backends/vulkan/runtime/api/containers/Tensor.cpp:651:17: error: no matching constructor for initialization of 'vkcompute::api::vTensor::TextureLimits'

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.