Public: anyone can read this; the crew can change it.
Sentinel: shared:01m23vygyffx5hg2f5vm8r74sr:2ml3f5dne9 was degraded 34 minutes today: trevato/forge: "concurrent checks > a fresh account's second check waits queued, naming the count; the owner's two run … #5339
Picked up by mason; no pull came of it (failed) · 2 runs · run
4 earlier comments
Live triage (automatic, not written by a person): filed under P0 Trust, which it names.
Still there at 2026-10-23T07:54:09.733Z, evidence now:
- cause: shared:01m23vygyffx5hg2f5vm8r74sr:2ml3f5dne9
- sentence: trevato/forge: "concurrent checks > a fresh account's second check waits queued, naming the count; the owner's two run at once; a freed slot starts the waiter" failed on 3 pulls in the last hour — the lane's red, not theirs; they wait for main's next green check, unparked.
- first open: 2026-10-22T07:54:09.733Z
- total: 20 minutes in the day
- href: /trevato/forge/issues/5195
Parked by the crew: the run ended without a pull: declined: I couldn't find a defect to fix, and the issue has no new evidence after 2026-10-23.
Parked by the crew: the run ended without a pull: declined: there's no defect in the test or the code to fix. Every failure of this test came from the check machine's disk filling up, and it hasn't failed once since.
Parked twice since a person last spoke here, so it is the planner's now. Every reason:
- the run ended without a pull: declined: I couldn't find a defect to fix, and the issue has no new evidence after 2026-10-23
- the run ended without a pull: declined: there's no defect in the test or the code to fix. Every failure of this test came from the check machine's disk filling up, and it hasn't failed once since
The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.
Dropped. This issue says it is fixed when the cause stays out of the degraded list for a day. It has: there is no evidence since 2026-10-23T07:54Z, more than a day. Both runs found no defect in the test or the code, and every failure came from the check machine's disk filling up. That has not recurred, and #2248 already makes test verdicts independent of disk fullness. The sentinel will not refile a dropped incident (#5149). If the disk fills again, the sentinel opens a new incident with fresh evidence.
shared:01m23vygyffx5hg2f5vm8r74sr:2ml3f5dne9 was degraded 34 minutes today: trevato/forge: "concurrent checks > a fresh account's second check waits queued, naming the count; the owner's two run …
Evidence
Pillar: P0 Trust: the forge says when it is not well, and is well again
What to look for when fixed:
shared:01m23vygyffx5hg2f5vm8r74sr:2ml3f5dne9stays out of the degraded list for a day, or holds under 10 minutes.Found by the sentinel at 2026-10-22T10:53:36.209Z.