-
Notifications
You must be signed in to change notification settings - Fork 687
Cadence: Warning if reference kernels not implemented for registered ops #15130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/15130
Note: Links to docs will display an error until the docs builds have been completed. ❌ 2 New FailuresAs of commit bf10bf4 with merge base 8fa1e38 ( NEW FAILURES - The following jobs have failed:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
This PR needs a
|
…ops (pytorch#15130) Summary: I ran into a problem where some new ops were checked into ops_registrations.py without an associated ref implementation. Any current meta kernels that don't have a reference we will warn on, but anything new will error out if no reference is provided. Differential Revision: D84650725
…ops (pytorch#15130) Summary: I ran into a problem where some new ops were checked into ops_registrations.py without an associated ref implementation. Any current meta kernels that don't have a reference we will warn on, but anything new will error out if no reference is provided. Differential Revision: D84650725
8f73055
to
bf10bf4
Compare
…ops (pytorch#15130) Summary: I ran into a problem where some new ops were checked into ops_registrations.py without an associated ref implementation. Any current meta kernels that don't have a reference we will warn on, but anything new will error out if no reference is provided. Differential Revision: D84650725
…ops (pytorch#15130) Summary: I ran into a problem where some new ops were checked into ops_registrations.py without an associated ref implementation. Any current meta kernels that don't have a reference we will warn on, but anything new will error out if no reference is provided. Differential Revision: D84650725
…ops (pytorch#15130) Summary: I ran into a problem where some new ops were checked into ops_registrations.py without an associated ref implementation. Any current meta kernels that don't have a reference we will warn on, but anything new will error out if no reference is provided. Differential Revision: D84650725
…ops (pytorch#15130) Summary: I ran into a problem where some new ops were checked into ops_registrations.py without an associated ref implementation. Any current meta kernels that don't have a reference we will warn on, but anything new will error out if no reference is provided. Differential Revision: D84650725
…ops (pytorch#15130) Summary: I ran into a problem where some new ops were checked into ops_registrations.py without an associated ref implementation. Any current meta kernels that don't have a reference we will warn on, but anything new will error out if no reference is provided. Differential Revision: D84650725
Summary: I ran into a problem where some new ops were checked into ops_registrations.py without an associated ref implementation. For now, I am warning for all of these situations, but once I can run without warnings, will error out instead.
Differential Revision: D84650725