NXP backend: Add Neutron backend to /backend/test/suite/operators testing.

[MartinPavella]

Summary

Use the testing suite in /backend/test/suite/operators to test the Neutron backend. Currently, all tests are passing except for 2 cat tests and all lstm tests due to known bugs in the NeutronConverter (so these tests are skipped).

Test plan

pytest -c /dev/nul backends/test/suite/operators/ -m backend_nxp -n auto

cc @robert-kalmar @JakeStevens @digantdesai @rascani

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

⏳ No Failures, 8 Pending

As of commit bfb2aa6 with merge base 92079a2 ():
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[linux-foundation-easycla]

• ❌ - login: @MartinPavella / name: Martin Pavella. The commit (0c9c0ff, 4e66ebe, 9584e5d, 9951cba, bfb2aa6, ed4936c) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please visit our EasyCLA portal and chat with our support bot.

[MartinPavella]

This change was introduced because the HardTanhConverter inherits from ClampConverter and uses its methods while overriding others. So only ClampConverter implements is_supported_on_target, which internally calls get_bounds which is implemented in botch classes differently. Therefore, is_supported_on_target must be a class method.

(It worked before this commit because the ClampConverter actually defined the is_supported_on_target as a class method, even thought its parent class NodeConverter declared is as a static method.)

[rascani]

Can you look into the test failures?

[MartinPavella]

Can you look into the test failures?

All fixed and ready for review.

[novak-vaclav]

I really like the integration into the community test harness, good job 🫵👍👍👍

I have a few comments, but nothing serious.

[rascani]

Take a look at test-backend-*.yml files. These all leverage the reusable _test_backend.yml, and we should probably create a test-backend-nxp.yml job. I recently also setup the backend test harness for cortex-m, you can probably use it as a template. #21854

[MartinPavella]

Thank you for pointing that out to me.
I have remove the test-nxp-testsuite-linux from pull.yml and instead I created a test-backend-nxp.yml which uses _test_backend.yml based on how you used it for Cortex-M in your PR.

Edit: The job passed and produced the expected test report.