Repository navigation
fix: retry invalid rescore caches - #377
Merged
Perry2004 merged 3 commits intoOct 17, 2026
Merged
Conversation
Perry2004
approved these changes
Oct 17, 2026
Perry2004
left a comment
Perry2004
left a comment
Collaborator
There was a problem hiding this comment.
LGTM 🫡
Thanks for the contribution! 🎊
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.
clawbench-rescoreskips runs with malformed judge caches, so they never reach the retry logic. This affects rescore scheduling for both rubrics.Use the same cache check when scheduling and judging, and write verdicts atomically. Incomplete runs now exit with an error.
Package:
clawbench.evalFiles:
rescore.py,test_rescore_corrupt_cache.py,CHANGELOG.mdTests: 9 related tests passed.
Fixes #364.