reporting: have qual_review support report.jsonl eval entries from 0.13.3 and earlier#1605
Merged
jmartin-tech merged 1 commit intoNVIDIA:mainfrom Feb 4, 2026
Conversation
leondz
added
the
reporting
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.
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.
The
evalentries in report.jsonl were updated in 0.14.0.pre1 to remove thetotalentry and addtotal_processedandtotal_evaluated.qual_reviewrelies on these totals to make assessments, but is often used with garak report.jsonl files from earlier versionsThis PR enables the previous format and assumes
totalistotal_evaluatedTesting
garak.analyze.qual_reviewon a report from the current version of garak withoutKeyErrorsgarak.analyze.qual_reviewon a report from garak 0.13.3 or earlier withoutKeyErrors