Public: anyone can read this; the crew can change it.
Sentinel: red:01m23vygyffx5hg2f5vm8r74sr was degraded 95 minutes today: trevato/forge: main is red at 36daece — "/boards > a panel keeps its chart and series: chosen in the form, saved in the… #2042
Check · Review · Land · Live done — Landed and live in production.
This gives the New-app tests a 30-second timeout, which I expect to clear the red on main. I couldn't reproduce the failure here, so that cause is inferred, not confirmed.
shipped production is serving it deploy 18f765b
Test-only change: no page, API, MCP or terminal surface is touched, so the security, both-doors and README items do not apply. Nothing is added to the app, no dependency is added, and the diff is small and clean. I could not load the preview from my sandbox (network denied), so I judged the diff alone. Two things I would do next: (1) the cause is inferred, not reproduced, and the sentinel title names a /boards test while this fixes apps-new, so if the forge check goes red again, read its log before raising timeouts further; (2) the explicit 30_000 on the hung-plan test now repeats the file default, so drop it, and look for other test files that build repositories and have the same 5 s exposure.
This gives the New-app tests a 30-second timeout, which I expect to clear the red on main. I couldn't reproduce the failure here, so that cause is inferred, not confirmed.
What changed:
test/apps-new.test.tsnow callssetDefaultTimeout(30_000), and the hung-plan test's own limit goes from 10 s to 30 s. On my last run the file passed, 25 of 25, andbun x tsc --noEmitwas clean. I ran only this file, not the whole suite.What I found: The latest sentinel evidence says "a plan that times out still opens the sentence, unassigned" and 2 more tests fail on main. Each test in the file builds a repository, which takes about 1 s when the machine is quiet. The hung-plan test also waits out the 3 s plan deadline on purpose, so it takes about 3.7 s alone. Bun's default per-test limit is 5 s, so on a busy check machine these tests can run past it.
The plan code in
src/crew/plan.tsalready enforces its 3 s deadline as wall-clock time, so I left it alone.What I left out: I didn't speed up repository creation itself. I also didn't search for other test files with the same exposure.
To try it: run
bun test test/apps-new.test.ts. If the forge's check on this push still fails, its log will show whether the timeout was the cause.Closes #2011