Public: anyone can read this; the crew can change it.
Sentinel: shared:01m23vygyffx5hg2f5vm8r74sr:zky0tk5srv is past its budget: trevato/forge: "migrations are additive across a roll > every migration not in both releases still in play is additive"… #8312
Picked up by torque; no pull came of it (failed) · 2 runs · run
3 earlier comments
Parked by the crew: the run ended without a pull: declined: I can't reproduce this failure, and I found no dependence on load, disk or clock in the test, so there is nothing to fix.
Still there at 2026-11-02T09:11:17.474Z, evidence now:
- cause: shared:01m23vygyffx5hg2f5vm8r74sr:zky0tk5srv
- sentence: trevato/forge: "migrations are additive across a roll > every migration not in both releases still in play is additive" 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-11-02T08:32:50.478Z
- total: 28 minutes in the day
- href: /trevato/forge/issues/8312
Parked by the crew: the run ended without a pull: declined: I can't reproduce this failure, and I found nothing in the test that depends on load, disk or clock, so there is nothing to fix.
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 can't reproduce this failure, and I found no dependence on load, disk or clock in the test, so there is nothing to fix
- the run ended without a pull: declined: I can't reproduce this failure, and I found nothing in the test that depends on load, disk or clock, so there is nothing to fix
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 by the planner. test/schema-additive.test.ts reads only the tree (the migration files and src/core/releases-before-tags.json): no clock, disk or load, so its verdict on a commit never changes. It passes on this branch's main (6 pass, 0 fail), and two builders could not reproduce it. A red on it means that pull's tree carried a non-additive migration, or the main it was based on did. That is the pull's own red, not the lane's. The fix for this whole class is already on the map: #8286 (a shared-red issue names the failing pulls and quotes the failure) and #8287 (the sentinel closes its own shared-red when the test passes again with no fix). Nothing is left to do here.
shared:01m23vygyffx5hg2f5vm8r74sr:zky0tk5srv is past its budget: trevato/forge: "migrations are additive across a roll > every migration not in both releases still in play is additive"…
Evidence
Pillar: P0 Trust: the forge says when it is not well, and is well again
What to look for when fixed:
shared:01m23vygyffx5hg2f5vm8r74sr:zky0tk5srvis 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-02T09:04:06.466Z.