You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 512d1c7
Browse filesBrowse the repository at this point in the historyBrowse files
test(composed): scale the WP13 start watchdogs to the CI floor
Six WP13 acceptance cases fail on the Windows shards with "timed out waiting
for runtime-port record". The diagnostic added in the previous commit answered
what that meant: child exit=null with both streams still open. The child was
alive and still working — a slow start, not a crash.
These waits sit on a real `ocx start`: spawn a Bun runtime, load the CLI, read
config, bind a port, publish runtime-port.json. 10s is generous locally and is
not on a Windows shard running a quarter of the suite. The repository already
has the answer to exactly this class of flake — watchdogMs() with a 30s CI
floor, added when the macOS lane's 10s-floor watchdog fired at 10.16s — and
this suite never adopted it.
All three watchdogs move together, because they bound one lifecycle: the
runtime-port wait, the CLI watchdog, and the shutdown watchdog.
The per-case budget moves with them. A case can start a server twice and stop
it, so 45s would kill the case before a 30s watchdog inside it could report
anything — the budget has to exceed the sum of what it contains. 150s on CI,
unchanged locally.
Worth stating why the number matters here and not on the macOS lane: that lane
passes --timeout 60000, which would pre-empt any larger per-case value. The
Windows shards pass no --timeout at all, so Bun's 5s default applies and the
explicit per-case budget is the only ceiling that exists.
Refs #2108
Verification: 8 pass / 0 fail locally, ci-workflows 132 pass / 0 fail (it pins
the lane's timeout contract), tsc --noEmit exit 0. The Windows shard is the
only check that can prove the change, since the failure exists nowhere else.
0 commit comments