next still carries the pre-ruling 20s/30s test budget, so PR 34 will revert the org-wide ruling when it rebases
#48
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Found while checking the canonical test-timeout numbers on behalf of sneak/homoicon#122.
mainis ata868689— #42, merged 2026-08-10, implementing the org-wide ruling at #41 (comment): 60 s whole-suite hard cap, 20 s target with any overage filed as an improvement bug, andgo test -timeout 90sas the backstop.nextpredates that PR and still carries the superseded text inprompts/REPO_POLICIES.md: "must complete in under 20 seconds. Add a 30-second timeout", plus-timeout 30son both Go example lines (:470,:490,:492).#34 (
next->main) is currentlymergeable: false. When it is rebased or the conflict is resolved, whoever does it will be choosing between two versions of that paragraph with nothing marking which one is authoritative — and takingnext's side silently reverts the ruling in the one file every repo vendors. That is a quiet fleet-wide regression: repos re-vendoring afterwards would pick up 20 s/30 s again, and 30 s is the number measured to produce roughly 12% false-red builds on clean trees (evidence on sneak/homoicon#122).No ruling is needed — this is reconciling a branch against a decision already made.
Definition of done:
git grep -n 'timeout 30s'onnextis empty; the test-budget paragraph onnextmatchesmain's (60 s cap, 20 s target, 90 s backstop, and the sentence explaining that the backstop deliberately sits above the hard cap so it catches a hung test rather than a merely slow one); #34 reportsmergeable: true.