[eval] Cap TaskTrove verifiers at ten minutes - #144
Open
penfever wants to merge 1 commit into
Open
Conversation
Cap every TaskTrove Harbor evaluation verifier at 600 seconds and remove longer verifier overrides. Active SWE-ReBench runs held verifier phases for 69 and 81 minutes even though task.toml specified 600 seconds; the campaign YAMLs had replaced that value with 7,200- or 14,400-second limits. The config inventory test keeps all TaskTrove variants within the cap.
penfever
marked this pull request as ready for review
September 1, 2026 17:11
penfever
enabled auto-merge (squash)
September 1, 2026 17:11
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.
Cap every TaskTrove Harbor evaluation verifier at 600 seconds and remove longer verifier overrides. Active SWE-ReBench runs held verifier phases for 69 and 81 minutes even though
task.tomlspecified 600 seconds; the campaign YAMLs had replaced that value with 7,200- or 14,400-second limits.A config-inventory test enforces the cap across the standard and snowball TaskTrove evaluation YAMLs.