Public: anyone can read this; the crew can change it.
Full suite red: test/spawn-cell.test.ts #12816
Check · Review · Land · Live done — Landed and live in production.
I moved the real child forge boot out of test/spawn-cell.test.ts into a new test/spawn-cell-real-child.test.ts. I couldn't confirm the 29.8 s was that boot, since the sandbox runs both files with cells skipped, and I haven't seen the 29.8 s run's log. bun x tsc --noEmit and bun scripts/gate.ts pass here.
shipped production is serving it deploy 5bb6da3
6 earlier comments
I moved the real child forge boot out of test/spawn-cell.test.ts into a new test/spawn-cell-real-child.test.ts. I couldn't confirm the 29.8 s was that boot, since the sandbox runs both files with cells skipped, and I haven't seen the 29.8 s run's log. bun x tsc --noEmit and bun scripts/gate.ts pass here. Both spawn-cell files together give 37 pass, 3 skip, 0 fail, the same 40 tests as before. In the sandbox the whole file ran in 5.8 s, so the overrun only shows on the gate box.
- Why I split it: The
beforeAllthat boots a whole child forge in a bwrap cell (up to 85 s allowed) only runs where bwrap and socat exist. I assumed that boot was the file's time and the cause of the overrun. - What changed:
- The cellTools check, the seenChild helper and the "a real child forge" describe moved over unchanged.
- Their imports moved with them.
- Unused imports are removed from the old file.
- scripts/gate.ts gets a SLOW entry for the new file, citing #12793.
- What I chose not to do: I did not speed up the boot itself. The new file may still sit near the 20 s file budget on the gate box, which is why it's in SLOW. If its boot turns out fast, drop the entry.
To try it: bun test ./test/spawn-cell.test.ts ./test/spawn-cell-real-child.test.ts. The forge's full check on this push will show whether spawn-cell.test.ts is back under budget.
I made no change and pushed nothing. As far as I can tell, this isn't a failure my pull caused.
- What the log says: The preview came up. It reports "running at https://lab--12816--forge-trevato-apps.open-platform.sh · no tests declared, none run". The log you pasted is only routine periodic lines (process counts, SQL statements by caller) from a running forge. It shows no error and no crash.
- Why "no tests declared":
forge.jsonhas noapp.teststep. Its tests live undercheck(fast,run,verify), which the forge runs separately, and I haven't seen its verdict on this push. So the preview step has nothing to run, and that was already true before my change. - What my change touches: It only moves a test block into a new test file and adds one SLOW entry to
scripts/gate.ts. Nothing insrc/orforge.jsonchanged.bun scripts/gate.tsandbun x tsc --noEmitboth pass on the branch, and the two spawn-cell test files give 37 pass, 3 skip, 0 fail.
If the preview step really is meant to fail on "no tests declared", the fix is to add an app.test command to forge.json. That would change how every preview of this repo deploys, so I haven't done it. Tell me if you want it, and what command it should run. If this deploy failed for some other reason, send me the part of the log that names it.
Nothing new to push: my earlier commit on this branch already splits the file, and the latest full-suite run (check run 01m7dyeagt5mr3gjrp7w0z3qxw, c0a5a9c) came back green.
The three red runs were all timing: the whole file took 27.5–29.7 s against the 20 s file budget. The green run was on main at c0a5a9c, which does not contain my split. test/spawn-cell.test.ts is unchanged on main since 28f939d71, so that run passed on load alone. A heavily loaded runner could push the file back over 20 s, which is why I kept the split.
What the branch holds: c12a10bbd moves the real child forge boot out of test/spawn-cell.test.ts into test/spawn-cell-real-child.test.ts. Together with the existing spawn-cell-* files, no single file carries the whole real-cell cost.
What I chose not to do: I did not add the file to SLOW in scripts/gate.ts, and I did not change any test assertions.
What I did not run: I ran no tests, gate or type check this turn, since I changed nothing. The forge's check runs on the pull.
To try it: bun test ./test/spawn-cell.test.ts and bun test ./test/spawn-cell-real-child.test.ts.
Still red in the full suite (check run 01m7e0ck061w8ych8gzgmndg96, 0e7f347).
the whole file took 25.3 s, over the 20 s file budget: make it faster, or name its file in SLOW in scripts/gate.ts with an issue
To reproduce:
bun test ./test/spawn-cell.test.ts
bun test ./test/spawn-cell.test.ts --rerun-each 10
The full suite ran it in shard 282/3284, 4 files at a time.
Still red on current main: check failed: gate: rule "a comment line is wrapped at 100 columns": test/spawn-cell-real-child.test.ts:7 is 148 long; rewrap it. Fix it and push.
Still red in the full suite (check run 01m7e23h7z3j9ypkzebfwnafg7, 1d071fd).
the whole file took 25.2 s, over the 20 s file budget: make it faster, or name its file in SLOW in scripts/gate.ts with an issue
To reproduce:
bun test ./test/spawn-cell.test.ts
bun test ./test/spawn-cell.test.ts --rerun-each 10
The full suite ran it in shard 276/3290, 4 files at a time.
This pull splits the real child-forge boot out of test/spawn-cell.test.ts into test/spawn-cell-real-child.test.ts, so the original file fits its time budget again (#12793). The last push also fixes the gate failure from the previous check.
- Gate fix: line 7 of
test/spawn-cell-real-child.test.tswas a 148-column comment. It is now wrapped over two lines, under the 100-column limit. - What I ran:
bun scripts/gate.tsandbun x tsc --noEmitpass.test/spawn-cell-real-child.test.tsandtest/spawn-cell.test.tsgive 37 pass, 3 skip, 0 fail. The skips are the cell tests this sandbox cannot run. - Not run: the full 92-file fast set that
scripts/fast.tsnamed. The forge's check runs it on the push. - Not changed: no test logic or behaviour; only the comment moved.
To try it: bun test test/spawn-cell-real-child.test.ts test/spawn-cell.test.ts.
Approved. A pure test move: the real-child boot block goes to its own file with its imports, the old file loses only unused imports, and the SLOW entry names issue 12793. No src/ or UI change, so there is no experience surface to break, and the gate and type check are reported green. Two things I would do next: (1) put the new SLOW line after spawn-cell-e2e to keep the list alphabetical (scripts/gate.ts:162). (2) Once the full check reports per-file times, confirm spawn-cell.test.ts is under 20 s and that the new file really needs its SLOW entry. The pull admits it did not measure either, and if the boot is fast the entry is noise.
I moved the real child forge boot out of
test/spawn-cell.test.tsinto a newtest/spawn-cell-real-child.test.ts. I couldn't confirm the 29.8 s was that boot, since the sandbox runs both files with cells skipped, and I haven't seen the 29.8 s run's log.bun x tsc --noEmitandbun scripts/gate.tspass here. Both spawn-cell files together give 37 pass, 3 skip, 0 fail, the same 40 tests as before. In the sandbox the whole file ran in 5.8 s, so the overrun only shows on the gate box.beforeAllthat boots a whole child forge in a bwrap cell (up to 85 s allowed) only runs where bwrap and socat exist. I assumed that boot was the file's time and the cause of the overrun.- The
cellToolscheck, theseenChildhelper and the "a real child forge" describe moved over unchanged. - Their imports moved with them. - Unused imports are removed from the old file. -scripts/gate.tsgets a SLOW entry for the new file, citing #12793.To try it:
bun test ./test/spawn-cell.test.ts ./test/spawn-cell-real-child.test.ts. The forge's full check on this push will show whetherspawn-cell.test.tsis back under budget.Closes #12793