[Test] Use roi_list variable instead of hardcoded values in ROI tensor creation #18145
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
ConvolutedDog
added a commit
to ConvolutedDog/tvm
that referenced
this pull request
Jul 14, 2025
Contributor
Author
|
@mshr-h Request a review. |
mshr-h
approved these changes
Jul 14, 2025
ShiboXing
pushed a commit
to ShiboXing/tvm
that referenced
this pull request
Aug 10, 2025
…r creation (apache#18145) Update test_frontend_onnx.py
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.
This PR replaces the hardcoded [0.0, 0.0, 0.0, 0.0] values with the roi_list variable when creating the ROI tensor, addressing an issue from the previous PR (#18138) where the ROI values weren't properly configurable.