Ok, so here's the order of operations on my Mac:

child_process.createSocket creates the this.stdout socket, which kicks off a call to Socket.Readable.read.
echo completes, calling this._handle.onexit from internal/child_process.js.
The child process calls flushStdio, which calls flush() on this.stdout, setting its state.flowing to true.
The read from step 1 finishes at this point, sees that state.flowing is true in readableAddChunk, emits the data and kicks off another read which hits EOF. In net.js's onread, the condition if (self._readableState.length === 0) prevails and the socket is destroyed, triggering the close event and a successful test.

And here's the order of operations on centos5:

child_process.createSocket creates the this.stdout socket, which kicks off a call to Socket.Readable.read.
The read from step 1 finishes at this point and sees that state.flowing is null in readableAddChunk, so it buffers the data and kicks off another read.
The read from step 2 finishes and gets EOF. In ChildProcess's onEofChunk, thanks to streams: update .readable/.writable to false #4083, stdout's .readable is set to false. Since we have buffered data, the stream does not close at this point.
echo completes, calling this._handle.onexit from internal/child_process.js.
The child process calls flushStdio, but since stdout.readable is false, it doesn't call resume on it.
That's all! stdout sits never closes, so the ChildProcess never closes and the test fails.

My 100% Mac pass rates were on a branch that didn't have #4083; pulling in that commit, I get a ~1% fail rate. On centos5 it fails every time.

So my view is that #4083 was a little hasty and didn't account for ChildProcess's expectation that stream.readable remains true after onEofChunk is called. If I take out the stream.readable = false; line from onEofChunk, the test passes on centos5 every time. Does that make sense?

CC @mscdex

Uh oh!

flaky test: test-child-process-flush-stdio #4125

Description

Activity

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions