Cadence: Warning if reference kernels not implemented for registered ops #15130
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🔗 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 445c7a4 with merge base 4c4f235 ( NEW FAILURES - The following jobs have failed:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
meta-cla
bot
added
the
CLA Signed
This PR needs a
|
DrJessop
pushed a commit
to DrJessop/executorch
that referenced
this pull request
Oct 14, 2025
…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
DrJessop
force-pushed
the
export-D84650725
branch
from
7b27971 to
8f73055
Compare
DrJessop
pushed a commit
to DrJessop/executorch
that referenced
this pull request
Oct 14, 2025
…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
DrJessop
force-pushed
the
export-D84650725
branch
from
8f73055 to
bf10bf4
Compare
DrJessop
pushed a commit
to DrJessop/executorch
that referenced
this pull request
Oct 14, 2025
…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
DrJessop
pushed a commit
to DrJessop/executorch
that referenced
this pull request
Oct 15, 2025
…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
DrJessop
pushed a commit
to DrJessop/executorch
that referenced
this pull request
Oct 15, 2025
…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
DrJessop
pushed a commit
to DrJessop/executorch
that referenced
this pull request
Oct 15, 2025
…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
DrJessop
pushed a commit
to DrJessop/executorch
that referenced
this pull request
Oct 15, 2025
…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
ethansfng
approved these changes
Oct 15, 2025
DrJessop
force-pushed
the
export-D84650725
branch
from
bf10bf4 to
41d0ebc
Compare
DrJessop
pushed a commit
to DrJessop/executorch
that referenced
this pull request
Oct 15, 2025
…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. Reviewed By: ethansfng 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. Reviewed By: ethansfng Differential Revision: D84650725
DrJessop
force-pushed
the
export-D84650725
branch
from
41d0ebc to
445c7a4
Compare
DrJessop
pushed a commit
to DrJessop/executorch
that referenced
this pull request
Oct 15, 2025
…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. Reviewed By: ethansfng Differential Revision: D84650725
DrJessop
pushed a commit
to DrJessop/executorch
that referenced
this pull request
Oct 15, 2025
…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. Reviewed By: ethansfng Differential Revision: D84650725
DrJessop
pushed a commit
to DrJessop/executorch
that referenced
this pull request
Oct 15, 2025
…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. Reviewed By: ethansfng Differential Revision: D84650725
DrJessop
pushed a commit
to DrJessop/executorch
that referenced
this pull request
Oct 15, 2025
…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. Reviewed By: ethansfng Differential Revision: D84650725
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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