Change to <= dispatch count regression checks. #19166
Merged
Conversation
This file contains 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
saienduri
requested review from
ScottTodd
and removed request for
stellaraccident
ScottTodd
approved these changes
Nov 15, 2024
|
thanks! |
zjgarvey
added a commit
that referenced
this pull request
Nov 15, 2024
This commit bumps Torch-MLIR to llvm/torch-mlir@c26ca8b. @vivekkhandelwal1 is in India time zone, so I'm re-posting this PR at head of main to address the CI failure which was unblocked by #19166 --------- Signed-off-by: Vivek Khandelwal <[email protected]> Co-authored-by: Vivek Khandelwal <[email protected]>
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.
This changes the equal check for dispatch regressions to a <= check. We should monitor the dispatch counts and update the golden values appropriately instead of failing on improvements.
ci-exactly: build_packages, regression_test