reclassify failures on judge errors#184
Open
raghavm243512 wants to merge 3 commits into
Open
Conversation
raghavm243512
force-pushed
the
pr/reclassify_fails
branch
from
July 20, 2026 16:44
7d0b56d to
a2568a3
Compare
raghavm243512
marked this pull request as ready for review
July 20, 2026 16:44
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
1 participant
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.
Add argument to reclassify runs if there was an error computing the judge metric that led to it being marked as failed. This does not waste money on reruns if the run is already a clean "this one failed", only if for example, a judge api key was missing and the record "fails" but you don't actually need to redo the simulation, you can just attempt to reclassify.
A difference between this and rerun-failed-metrics is that this actually promotes the record after re-rating
I also move the git provenance in the docker file because it reduces the push size from 1.5gb to 50 mb or so. much better development speed this way