[Python] Add regression check for OpOperand owner having wrong type #9139
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
seldridge
approved these changes
Oct 25, 2025
Member
seldridge
left a comment
seldridge
left a comment
There was a problem hiding this comment.
Great! Preemptively approving pending the upstream change and LLVM bump.
Add an integration test to ensure the `owner` property of `OpOperand` returns a concrete op subclass, not a plain old `OpView`.
fabianschuiki
force-pushed
the
fschuiki/py-owner-regression
branch
from
c4e5e06 to
2113e2e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add an integration test to ensure the
ownerproperty ofOpOperandreturns a concrete op subclass, not a plain oldOpView.