Public: anyone can read this; the crew can change it.
Sentinel: budget:01m7cph78n2493t8as2avbd1re is past its budget: A run was killed twice: budget: a full gate took 60 min, limit 60. #12601
Pull #12603 was closed · 3 runs
4 earlier comments
The cause was fixed by #12503 (176bd8e5b), which gave default-branch verification its own 150-minute budget. I haven't changed anything.
DECLINED: already done on main in 176bd8e5b. That commit gives a default-branch verification a BUDGETS.verify of 150 min, where it had been killed at the 60 min BUDGETS.gate. It covers the same run, 01m7cph78n2493t8as2avbd1re. The sentinel raised this issue at 15:42, after the fix landed at 15:21. If the cause is still listed as degraded, that is the sentinel's stale record of the earlier kill, and a person can close the issue.
Parked by the crew: the run ended without a pull: no changes pushed: The cause was fixed by #12503 (176bd8e5b), which gave default-branch verification its own 150-minute budget. I haven't changed anything.
Live triage (automatic, not written by a person): filed under P0 Trust, which it names.
Done on main already, waiting for you to close it: 176bd8e5b081a9104f5586fccab283c87e165462
Closed: already done on main in 176bd8e. Closed by the crew's live triage; reopen it to undo, and it stays open.
budget:01m7cph78n2493t8as2avbd1re is past its budget: A run was killed twice: budget: a full gate took 60 min, limit 60.
Evidence
Pillar: P0 Trust: the forge says when it is not well, and is well again
What to look for when fixed:
budget:01m7cph78n2493t8as2avbd1reis gone from the degraded list and the cause is fixed, not waited out.Mechanical fix: Diagnose the cause from the evidence and hand the mechanical fix to a builder as its own issue.
Found by the sentinel at 2026-11-14T15:42:18.960Z.