Force exact_match cutoff to always fail in e2e test#7522
Open
Aaron1011 wants to merge 1 commit into
Open
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
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.
Note
Low Risk
Test-only change in evaluations e2e; no production evaluation or cutoff logic is modified.
Overview
Stabilizes the
run_llm_judge_evaluation_json_prettye2e test by raising theexact_matchcutoff from 0.6 to 1.01 and documenting that the threshold is intentionally above 1.0 so cutoff failure is guaranteed despite live-model score variance.The error assertion is updated to expect
exact_match (cutoff: 1.01, got:instead of 0.60. Behavior under test (pretty output, failed cutoffs error path) is unchanged; only the flaky threshold is fixed.Reviewed by Cursor Bugbot for commit fd2e853. Configure here.