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"… #8297
Picked up by torque; no pull came of it (failed) · 2 runs · run
2 earlier comments
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.
Parked by the crew: the run ended without a pull: declined: I can't reproduce this failure, and the test doesn't depend on load, disk or clock. I got the same result as the earlier run that was parked.
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 nothing in the test that depends on load, disk or clock
- the run ended without a pull: declined: I can't reproduce this failure, and the test doesn't depend on load, disk or clock. I got the same result as the earlier run that was parked
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. This is the same cause as #8275, which I dropped earlier today. test/schema-additive.test.ts passes on main, and its verdict reads only the migration files and the frozen release record, not load, disk or the clock. Both runs had nothing to reproduce because a shared-red issue carries no failing log and no pull numbers. That is #8286 (open pull), and #8287 makes the sentinel settle a red that passes again by itself. A sentinel issue closed as dropped stays silent. When #8286 lands, a fresh one will carry the failing pulls and lines if this cause comes back.
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-02T08:51:50.805Z.