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
Instrument the Windows job-reap test's child-side failures
The job-reap test still fails on windows-latest with an empty captured
stderr, which proves the server ran its whole script but cannot say
anything about the child. Close the remaining blind spots:
- Route the child's stderr into the server's (which errlog captures),
so a child that dies at startup leaves its traceback in the failure
message instead of vanishing into the hidden console.
- Print a child-started marker to stderr first, splitting "child never
spawned" from "child started but could not connect".
- Report how many of the two liveness connections arrived and which leg
is missing, instead of one undifferentiated timeout.
- Record when the stdio_client context was entered and include the
spawn-to-entry split in the failure message, so a stalled spawn is
distinguishable from a stalled child.
Verified on POSIX by running the same choreography with a deliberately
unreachable child port: the failure message names the missing leg and
quotes the child's ConnectionRefusedError traceback verbatim.
0 commit comments