Public: anyone can read this; the crew can change it.
Sentinel: shared:01m23vygyffx5hg2f5vm8r74sr:10xbuym6wf is past its budget: trevato/forge: "build yield reads event through its index, never a scan of event or a run per run" failed on 3 pulls in… #12096
commented
Live triage (automatic, not written by a person): filed under P0 Trust, which it names.
commented
Still there at 2026-11-13T16:55:10.502Z, evidence now:
- cause: shared:01m23vygyffx5hg2f5vm8r74sr:10xbuym6wf
- sentence: trevato/forge: "build yield reads event through its index, never a scan of event or a run per run" failed on 4 pulls in the last hour — the lane's red, not theirs; they wait for main's next green check, unparked.
- first open: 2026-11-13T15:53:57.678Z
- total: 39 minutes in the day
- href: /trevato/forge/issues/12096
- test: build yield reads event through its index, never a scan of event or a run per run
- failed: pull #12091, check run 01m7as1sds0hc6ezfpx9a8621x
- base: [redacted] (run 01m7as1sds0hc6ezfpx9a8621x)
- log: 100 |
- log: 101 | test("build yield reads event through its index, never a scan of event or a run per run", () => {
- log: 102 | const plan = planOf(big, BUILD_YIELD_SQL, [ago(1440), ago(0), 0]);
- log: 103 | expect(plan.filter((d) => /SCAN /.test(d))).toEqual([]);
- log: 104 | expect(plan.some((d) => d.includes("event_repo_kind_number_at"))).toBe(true);
- log: 105 | expect(plan.some((d) => /SEARCH x USING INDEX run_kind_finished/.test(d))).toBe(true);
- log: ^
- log: error: expect(received).toBe(expected)
- log: Expected: true
- log: Received: false
- log: at <anonymous> (test/stall-scans.test.ts:105:78)
- main: passes on main's newest check, run 01m7ax0gybm7ectmdhs1ws5wjy at [redacted]
Sign in to join this conversation.
new above
offline
shared:01m23vygyffx5hg2f5vm8r74sr:10xbuym6wf is past its budget: trevato/forge: "build yield reads event through its index, never a scan of event or a run per run" failed on 3 pulls in…
Evidence
Pillar: P0 Trust: the forge says when it is not well, and is well again
What to look for when fixed:
shared:01m23vygyffx5hg2f5vm8r74sr:10xbuym6wfis gone from the degraded list and the cause is fixed, not waited out.Mechanical fix: Make the named test's verdict depend only on the code under test, not on the check machine's load, disk or clock, in one pull. Pulls red on it alone wait, unparked, for main's next green check.
Found by the sentinel at 2026-11-13T15:54:20.542Z.