Repository navigation
Conversation
case_wall_clock_budget looked up case["check_id"], but manifest cases name their CI/CD check cicd_check_id (as _cicd reads it). The lookup never matched, so every T3 case got the 780 s budget of a case with no declared timeout instead of one derived from its check's timeout_sec (6,124 s for a 379 s check). Current checks declare 300 to 379 s and fit under 780 s; a check declaring more than about 760 s would have been abandoned as an infrastructure failure inside its own timeout. The same one-line change is applied to all 70 copies of formal.py, which stay byte-identical. It changes the tasks' content hashes, so it ships with the next task release.
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
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.
Closes #49
case_wall_clock_budgetlooked upcase["check_id"], but manifest cases name their checkcicd_check_id, which_cicdalready reads. Every T3 case got the 780 s budget of a case with no declared timeout instead of one derived from its check'stimeout_sec.mediumcheck withtimeout_sec: 379Current checks declare 300 to 379 s, so no reward changes today. A check declaring more than about 760 s would have been abandoned inside its own timeout.
Release
The one-line change is applied to all 70 copies of
formal.py, which stay byte-identical. It changes the tasks' content hashes, so it ships with the next task release; the release index is untouched here.Verification
Budget computed with the
mediummanifest and CI/CD suite: 6,124 s for the 379 s check.scripts/check_tasks.py --code-only: 70 PASS.uv run python -m unittest discover -s testsuv run ruff check scripts src testsuv run ruff format --check scripts src tests