Uh oh!
There was an error while loading. Please reload this page.
test,dgram: harden test-dgram-bind-shared-ports.js - #13100
Conversation
refack
commented
May 18, 2017
gibfahn
commented
May 18, 2017
FWIW you can run node-test-commit or node-stress-single-test on a branch of your fork of Node if you want. |
refack
commented
May 18, 2017
Thanks, I was vaguely aware of that, but was not sure... |
There was a problem hiding this comment.
FWIW, I think this will only fire in the second worker. The first worker doesn't get an error on socket2 (and it's the first worker we care about for socket2 because it actually binds to the port).
Starting to wonder if whatever complexity is required to make socket2.close() work isn't any greater than complexity that might be required to make port: 0 work for this test. :-|
refack
commented
May 18, 2017
Is that a wink? |
b0381e0 to
45323f0Comparerefack
commented
May 18, 2017
refack
commented
May 19, 2017
Found a bug when workers bind for port 0. Blocking until I fix it. |
fhinkel
commented
Jun 7, 2017
cluster to share sockets when worker bind to port 0refack
commented
Jun 8, 2017
Dry-run CI: https://ci.nodejs.org/job/node-test-pull-request/8551/ |
refack
commented
Jun 9, 2017
Landed in c9d45c4 |
refack
commented
Jun 9, 2017
Extra sanity of |
MylesBorins
commented
Jul 17, 2017
@refack could you please backport to v6.x? |
* add `mustCall` and `mustNotCall` to all callbacks * added `known_issue` for port binding PR-URL: nodejs#13100 Refs: nodejs#13055 Refs: nodejs#12999 Refs: nodejs#13526 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
mustCallandmustNotCallto all callbacksexitthe processes instead ofkillRef: #13055
Ref: #12999
Ref: #13526
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passesAffected core subsystem(s)
dgram,cluster,test