test-cluster-net-send failure on windows #3957
Comments
Fishrock123
added
windows
Trott
added a commit
to Trott/io.js
that referenced
this issue
Nov 24, 2015
See nodejs#3957 for details and examples failures. Ref: nodejs#3957
Trott
added a commit
to Trott/io.js
that referenced
this issue
Nov 25, 2015
See nodejs#3957 for details and examples failures. Ref: nodejs#3957 Reviewed-By: Ben Noordhuis <[email protected]> PR-URL: nodejs#4006
Trott
added a commit
that referenced
this issue
Dec 1, 2015
See #3957 for details and examples failures. Ref: #3957 Reviewed-By: Ben Noordhuis <[email protected]> PR-URL: #4006
Trott
added a commit
that referenced
this issue
Dec 4, 2015
See #3957 for details and examples failures. Ref: #3957 Reviewed-By: Ben Noordhuis <[email protected]> PR-URL: #4006
Trott
added a commit
that referenced
this issue
Dec 5, 2015
See #3957 for details and examples failures. Ref: #3957 Reviewed-By: Ben Noordhuis <[email protected]> PR-URL: #4006
Trott
added a commit
that referenced
this issue
Dec 17, 2015
See #3957 for details and examples failures. Ref: #3957 Reviewed-By: Ben Noordhuis <[email protected]> PR-URL: #4006
Trott
added a commit
that referenced
this issue
Dec 23, 2015
See #3957 for details and examples failures. Ref: #3957 Reviewed-By: Ben Noordhuis <[email protected]> PR-URL: #4006
mscdex
added a commit
to mscdex/io.js
that referenced
this issue
Dec 29, 2015
Before this commit, it was possible on Windows for the server's 'connection' handler to be called *after* the client socket's 'connect' handler. This caused the 'message' event to be missed and the test would never end (timing out in CI). This problem was more easily reproducible on a low resource (slow CPU) Windows (2012r2) installation. This commit waits until both handlers have been called before sending the handle to the master process. Fixes: nodejs#3957 PR-URL: nodejs#4444
Fishrock123
pushed a commit
to Fishrock123/node
that referenced
this issue
Jan 6, 2016
Before this commit, it was possible on Windows for the server's 'connection' handler to be called *after* the client socket's 'connect' handler. This caused the 'message' event to be missed and the test would never end (timing out in CI). This problem was more easily reproducible on a low resource (slow CPU) Windows (2012r2) installation. This commit waits until both handlers have been called before sending the handle to the master process. Fixes: nodejs#3957 PR-URL: nodejs#4444 Reviewed-By: Rich Trott <[email protected]>
MylesBorins
pushed a commit
that referenced
this issue
Jan 28, 2016
Before this commit, it was possible on Windows for the server's 'connection' handler to be called *after* the client socket's 'connect' handler. This caused the 'message' event to be missed and the test would never end (timing out in CI). This problem was more easily reproducible on a low resource (slow CPU) Windows (2012r2) installation. This commit waits until both handlers have been called before sending the handle to the master process. Fixes: #3957 PR-URL: #4444 Reviewed-By: Rich Trott <[email protected]>
MylesBorins
pushed a commit
that referenced
this issue
Feb 11, 2016
Before this commit, it was possible on Windows for the server's 'connection' handler to be called *after* the client socket's 'connect' handler. This caused the 'message' event to be missed and the test would never end (timing out in CI). This problem was more easily reproducible on a low resource (slow CPU) Windows (2012r2) installation. This commit waits until both handlers have been called before sending the handle to the master process. Fixes: #3957 PR-URL: #4444 Reviewed-By: Rich Trott <[email protected]>
MylesBorins
pushed a commit
to MylesBorins/node
that referenced
this issue
Feb 11, 2016
Before this commit, it was possible on Windows for the server's 'connection' handler to be called *after* the client socket's 'connect' handler. This caused the 'message' event to be missed and the test would never end (timing out in CI). This problem was more easily reproducible on a low resource (slow CPU) Windows (2012r2) installation. This commit waits until both handlers have been called before sending the handle to the master process. Fixes: nodejs#3957 PR-URL: nodejs#4444 Reviewed-By: Rich Trott <[email protected]>
MylesBorins
pushed a commit
to MylesBorins/node
that referenced
this issue
Feb 15, 2016
Before this commit, it was possible on Windows for the server's 'connection' handler to be called *after* the client socket's 'connect' handler. This caused the 'message' event to be missed and the test would never end (timing out in CI). This problem was more easily reproducible on a low resource (slow CPU) Windows (2012r2) installation. This commit waits until both handlers have been called before sending the handle to the master process. Fixes: nodejs#3957 PR-URL: nodejs#4444 Reviewed-By: Rich Trott <[email protected]>
scovetta
pushed a commit
to scovetta/node
that referenced
this issue
Apr 2, 2016
See nodejs#3957 for details and examples failures. Ref: nodejs#3957 Reviewed-By: Ben Noordhuis <[email protected]> PR-URL: nodejs#4006
scovetta
pushed a commit
to scovetta/node
that referenced
this issue
Apr 2, 2016
Before this commit, it was possible on Windows for the server's 'connection' handler to be called *after* the client socket's 'connect' handler. This caused the 'message' event to be missed and the test would never end (timing out in CI). This problem was more easily reproducible on a low resource (slow CPU) Windows (2012r2) installation. This commit waits until both handlers have been called before sending the handle to the master process. Fixes: nodejs#3957 PR-URL: nodejs#4444 Reviewed-By: Rich Trott <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://ci.nodejs.org/job/node-test-binary-windows/91/RUN_SUBSET=3,VS_VERSION=vs2015,label=win2012r2/tapTestReport/test.tap-25/
(Failed against #3954, unrelated.)
The text was updated successfully, but these errors were encountered: