reporting: aggregate probe as min#1218
Merged
leondz merged 2 commits intoNVIDIA:mainfrom May 19, 2025
Merged
Conversation
erickgalinkin
approved these changes
May 19, 2025
Collaborator
erickgalinkin
left a comment
There was a problem hiding this comment.
I am very into this change.
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
probe-level results over multiple detectors were aggregated as mean in html report
this cuts too much signal out when detectors pick up failures
aggregate as minimum instead
e.g. when detectors report 100% and 0% pass, aggregate result on top line shows now minimum, 0%