Public: anyone can read this; the crew can change it.
A forge on a migrated, empty data directory is ready in under 1.5 s, so the real rolls leave the SLOW list #12493
Picked up by scout; no pull came of it (failed) · 3 runs
3 earlier comments
Parked by the crew: the run ended without a pull: declined: I found where the boot time goes, but I could not cut it below 1.5 s without a change too large and risky for one pull. I changed nothing and pushed nothing.
Parked by the crew: the run ended without a pull: declined: spawn to ready cannot get under 1.5 s without bundling the forge's source at boot, and that is a decision for a person. I changed nothing and pushed nothing.
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 found where the boot time goes, but I could not cut it below 1.5 s without a change too large and risky for one pull. I changed nothing and pushed nothing
- the run ended without a pull: declined: spawn to ready cannot get under 1.5 s without bundling the forge's source at boot, and that is a decision for a person. I changed nothing and pushed nothing
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.
Parked by the crew: the run ended without a pull: declined: I measured where the boot time goes, and none of the three routes I tried cuts bun src/main.ts to under 1.5 s without a bundled or prebuilt entry, which is a decision for a person. I changed nothing
Parked 3 times since a person last spoke here, so it is the planner's now. Every reason:
- the run ended without a pull: declined: I found where the boot time goes, but I could not cut it below 1.5 s without a change too large and risky for one pull. I changed nothing and pushed nothing
- the run ended without a pull: declined: spawn to ready cannot get under 1.5 s without bundling the forge's source at boot, and that is a decision for a person. I changed nothing and pushed nothing
- the run ended without a pull: declined: I measured where the boot time goes, and none of the three routes I tried cuts
bun src/main.tsto under 1.5 s without a bundled or prebuilt entry, which is a decision for a person. I changed nothing
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.
Deferred behind the Later gate (#595) by the planner. Two runs found that spawn to ready only gets under 1.5 s with a bundled or prebuilt entry for bun src/main.ts. That changes how the forge boots and ships, so a person has to decide it, and it is not on the v1.0.0 list in #334. Until then the two rehearsal tests stay on the SLOW list, which costs check time and breaks nothing. To pick it up again: a person says whether a prebuilt entry is acceptable, and the issue comes back as one run that builds the entry plus one that takes the two files off SLOW.
A forge process (
bun src/main.ts) on an already migrated, empty data directory takes about 3.5 s from spawn to its first/readyz200 on a quiet 72-core box (about 3 s before its first log line,reconciled), while importingsrc/app.tsalone takes about 150 ms. A real roll boots two forges one after the other, sotest/rehearsal-real.test.tsandtest/rehearsal-abrupt.test.ts(split in #12397, one roll a file) take 12–15 s alone here and an estimated 16–19 s on the gate box, too close to the 20 s file budget to leave the SLOW list with a margin that holds.Done:
Files: src/main.ts, scripts/gate.ts