Op registry to warn instead of error against duplicated op s (#18179)

[rezaasjd]

Summary:

Resolves the issue where duplicated primitive ops can be attempted to be registered from multiple ET runners.
The error can be silent in pre-main static intialization.

Differential Revision: D96544230

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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

As of commit 4b8bcbc with merge base d0820e1 ():

NEW FAILURE - The following job has failed:

• Lint / lintrunner (gh)
  >>> Lint for runtime/kernel/test/operator_registry_test.cpp:

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

[meta-codesync]

@rezaasjd has exported this pull request. If you are a Meta employee, you can view the originating Diff in D96544230.

[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.

[kirklandsign]

What's the use case of multiple runners?

[rezaasjd]

What's the use case of multiple runners?

multiple subsystem are running their own et runner. For instance, an MCU thread where its running ET runner for model x, and a DSP thread where it's running a separate ET runner for model Y.