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 d2f1dcc
Browse filesBrowse the repository at this point in the historyBrowse files
test(composed): show the child's output when a start never publishes its port
Six of the WP13 acceptance tests fail on the Windows shards with "timed out
waiting for runtime-port record". That message is the symptom and never the
cause: the child process writes runtime-port.json only after a successful
start, so the interesting information — a throw, a bind refusal, a missing
artifact — is in its stderr, which the fixture piped and then discarded.
Two CI rounds read as "Windows is flaky" for exactly this reason. This makes
the next round say what actually happened.
The streams are captured once at spawn and carried on StartedServer, because a
Bun subprocess stream cannot be read twice — the Grok E2E case already reads
stdout after start() and would otherwise fail with "ReadableStream has already
been used". Caught locally before pushing.
Diagnostic only: no production code, and the failure message is the only
behavior that changes.
Refs #2108
0 commit comments