You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Mutation run: a shard whose baseline fails names the tests that failed, and tests.test_tools.Trials is brought down from 463 s #438
tests.test_tools.Trials takes 463 s on a desk, unmutated (33 tests, read 2026-10-30). A full make verify now takes about 24 minutes, and AGENTS.md still says half a minute. Mutation run: a mutant names the method that kills it, never a class too slow to run whole #437 stops mutants from naming that class whole, but it remains the largest part of every verify and of the stop hook's 579 s timeout.
Done when
A failing baseline prints the failing tests' names, each with its first line of error, within a bound that keeps the log readable.
Trials is measured test by test, and what is slow is named. Bring it down where the time is not what the test asserts, without dropping a case.
AGENTS.md's Verify section states the real time, so tools/check_context.py's reader isn't misled.
Say whether the stop hook should keep running a whole verify, given that it times out on every builder's turn.
Activity
Mutation run: a failing baseline names its tests, and the trials chec…