Public: anyone can read this; the crew can change it.

Sentinel: shared:01m23vygyffx5hg2f5vm8r74sr:19547qkh3k is past its budget: trevato/forge: "a walk that blows up half-way (outside any step) still removes its forge" failed on 3 pulls in the last… #12457

shipped production is serving it opened this has it

Landed in pull #12458 · 2 runs · run

opened this

shared:01m23vygyffx5hg2f5vm8r74sr:19547qkh3k is past its budget: trevato/forge: "a walk that blows up half-way (outside any step) still removes its forge" failed on 3 pulls in the last…

Evidence

  • cause: shared:01m23vygyffx5hg2f5vm8r74sr:19547qkh3k
  • sentence: trevato/forge: "a walk that blows up half-way (outside any step) still removes its forge" failed on 3 pulls in the last hour — the lane's red, not theirs; they wait for main's next green check, unparked.
  • since: 2026-11-14T07:16:22.846Z
  • href: /trevato/forge/issues/new
  • test: a walk that blows up half-way (outside any step) still removes its forge
  • failed: pull #12227, check run 01m7cb1vjnmbzqf6qgbkd2wa51
  • failed: pull #12278, check run 01m7ca75d8ny08ty8jrw5drr7m
  • failed: pull #12345, check run 01m7c98rp55s48hxh2258ddmdx
  • base: [redacted] (run 01m7cb1vjnmbzqf6qgbkd2wa51)
  • log: 182 | expect(result.removed).toBe(true);
  • log: 183 | expect(log).toContain("POST /claim");
  • log: 184 | const name = [...kids.keys()].at(-1)!;
  • log: 185 | expect(await forgeGone(name)).toBe(true);
  • log: 186 | // The account lived in the forge's own data: that directory is gone, and the account with it.
  • log: 187 | expect(existsSync(kids.get(name)!.dataDir)).toBe(false);
  • log: ^
  • log: error: expect(received).toBe(expected)
  • log: Expected: false
  • log: Received: true
  • log: at <anonymous> (test/release-journey.test.ts:187:47)
  • main: passes on main's newest check, run 01m7bhyf02fje76g09qbmmhtsp at [redacted]

Pillar: P0 Trust: the forge says when it is not well, and is well again

What to look for when fixed: shared:01m23vygyffx5hg2f5vm8r74sr:19547qkh3k is 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-14T07:16:30.096Z.

commented

Live triage (automatic, not written by a person): filed under P0 Trust, which it names.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs