Revision cb1646f4
| ID | cb1646f44eb092f1771740fc5f0ec6775d5fbe73 |
| Parent | 876d3bd8 |
| Child | 13de0f1d |
test: fix assumption of worker exit on disconnect
Master was disconnecting its workers as soon as they both started up.
Meanwhile, the workers were trying to listen. Its a race, sometimes the
disconnect would happen between when worker gets the response message,
and acks that message with a 'listening'. This worked OK after v0.11
introduced a behaviour where disconnect would always exit the worker,
but once that backwards-incompatible behaviour is removed, the worker
lives long enough to try and respond to the master, and child_process
errors at the attempt to send from a disconnected child.
Files
- added
- modified
- copied
- renamed
- deleted