Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate flaky test-net-GH-5504 #6611

Closed
Trott opened this issue May 6, 2016 · 7 comments
Closed

Investigate flaky test-net-GH-5504 #6611

Trott opened this issue May 6, 2016 · 7 comments
Labels
net Issues and PRs related to the net subsystem. test Issues and PRs related to the tests. windows Issues and PRs related to the Windows platform.

Comments

@Trott
Copy link
Member

Trott commented May 6, 2016

Failure:

@Trott Trott added the test Issues and PRs related to the tests. label May 6, 2016
@mscdex mscdex added the net Issues and PRs related to the net subsystem. label May 6, 2016
@santigimeno
Copy link
Member

I include the error, just in case the link is gone:

not ok 1113 test-net-GH-5504.js
# SERVER 2>NET 14244: listen2 null 12346 4 false undefined
# SERVER 2>NET 14244: _listen2: create a handle
# SERVER 2>NET 14244: bind to ::
# CLIENT 2>NET 14249: createConnection [ { host: 'localhost', port: 12346 }, [Function] ]
# CLIENT 2>NET 14249: pipe false undefined
# CLIENT 2>NET 14249: connect: find host localhost
# CLIENT 2>NET 14249: connect: dns options { family: undefined, hints: 32 }
# CLIENT 2>NET 14249: afterConnect
# CLIENT 2>NET 14249: destroy undefined
# CLIENT 2>NET 14249: destroy
# CLIENT 2>NET 14249: close
# CLIENT 2>NET 14249: close handle
# CLIENT 2>NET 14249: _read
# CLIENT 2>NET 14249: _read wait for connection
# CLIENT 2>NET 14249: emit close
# SERVER 2>NET 14244: onconnection
# SERVER 2>NET 14244: _read
# SERVER 2>NET 14244: Socket._read readStart
# SERVER 2>NET 14244: SERVER _emitCloseIfDrained
# SERVER 2>NET 14244: SERVER handle? false   connections? 1
# SERVER 2>NET 14244: afterWrite -32
# SERVER 2>NET 14244: write failure { Error: write EPIPE
# SERVER 2>    at exports._errnoException (util.js:949:11)
# SERVER 2>    at WriteWrap.afterWrite (net.js:793:14) code: 'EPIPE', errno: 'EPIPE', syscall: 'write' }
# SERVER 2>NET 14244: destroy
# SERVER 2>NET 14244: close
# SERVER 2>NET 14244: close handle
# SERVER 2>events.js:160
# SERVER 2>      throw er; // Unhandled 'error' event
# SERVER 2>      ^
# SERVER 2>
# SERVER 2>Error: write EPIPE
# SERVER 2>    at exports._errnoException (util.js:949:11)
# SERVER 2>    at WriteWrap.afterWrite (net.js:793:14)
# server exited 1
# client exited 0
# /home/iojs/build/workspace/node-test-commit-linux/nodes/fedora21/test/sequential/test-net-GH-5504.js:66
# throw new Error('hang');
# ^
# 
# Error: hang
# at Timeout._onTimeout (/home/iojs/build/workspace/node-test-commit-linux/nodes/fedora21/test/sequential/test-net-GH-5504.js:66:13)
# at tryOnTimeout (timers.js:224:11)
# at Timer.listOnTimeout (timers.js:198:5)
# SERVER 1>listening
# ok

@Trott Trott added the windows Issues and PRs related to the Windows platform. label May 20, 2016
@Trott
Copy link
Member Author

Trott commented May 20, 2016

Failed on win10 today too: https://ci.nodejs.org/job/node-test-binary-windows/2198/RUN_SUBSET=2,VS_VERSION=vcbt2015,label=win10/tapTestReport/test.tap-282/

not ok 282 c:\workspace\node-test-binary-windows\RUN_SUBSET\2\VS_VERSION\vcbt2015\label\win10\test\sequential\test-net-GH-5504
# SERVER 2>NET 3288: listen2 null 12346 4 false undefined
# SERVER 2>NET 3288: _listen2: create a handle
# SERVER 2>NET 3288: bind to ::
# C:\workspace\node-test-binary-windows\RUN_SUBSET\2\VS_VERSION\vcbt2015\label\win10\test\sequential\test-net-GH-5504.js:66
# throw new Error('hang');
# ^
# 
# Error: hang
# at Timeout._onTimeout (C:\workspace\node-test-binary-windows\RUN_SUBSET\2\VS_VERSION\vcbt2015\label\win10\test\sequential\test-net-GH-5504.js:66:13)
# at tryOnTimeout (timers.js:224:11)
# at Timer.listOnTimeout (timers.js:198:5)
# SERVER 1>listening

@Trott
Copy link
Member Author

Trott commented May 21, 2016

Another on win10: https://ci.nodejs.org/job/node-test-binary-windows/2211/RUN_SUBSET=2,VS_VERSION=vcbt2015,label=win10/console

not ok 282 c:\workspace\node-test-binary-windows\RUN_SUBSET\2\VS_VERSION\vcbt2015\label\win10\test\sequential\test-net-GH-5504
# SERVER 2>NET 4152: listen2 null 12346 4 false undefined
# SERVER 2>NET 4152: _listen2: create a handle
# SERVER 2>NET 4152: bind to ::
# CLIENT 2>NET 1620: createConnection [ { host: 'localhost', port: 12346 }, [Function] ]
# CLIENT 2>NET 1620: pipe false undefined
# CLIENT 2>NET 1620: connect: find host localhost
# CLIENT 2>NET 1620: connect: dns options { family: undefined, hints: 1024 }
# SERVER 2>NET 4152: onconnection
# SERVER 2>NET 4152: _read
# SERVER 2>NET 4152: Socket._read readStart
# SERVER 2>NET 4152: SERVER _emitCloseIfDrained
# SERVER 2>NET 4152: SERVER handle? false   connections? 1
# C:\workspace\node-test-binary-windows\RUN_SUBSET\2\VS_VERSION\vcbt2015\label\win10\test\sequential\test-net-GH-5504.js:66
#       throw new Error('hang');
#       ^
# 
# Error: hang
#     at Timeout._onTimeout (C:\workspace\node-test-binary-windows\RUN_SUBSET\2\VS_VERSION\vcbt2015\label\win10\test\sequential\test-net-GH-5504.js:66:13)
#     at tryOnTimeout (timers.js:224:11)
#     at Timer.listOnTimeout (timers.js:198:5)
# SERVER 1>listening
  ---
  duration_ms: 3.224

@Trott
Copy link
Member Author

Trott commented Jul 1, 2016

Stress test on everything to see where this is reproducible and still an issue: https://ci.nodejs.org/job/node-stress-single-test/772/

@Trott
Copy link
Member Author

Trott commented Jul 2, 2016

Flaky on win2008r2-1p:

1234   OK: 1234   NOT OK: 0   TOTAL: 9999
1..1
not ok 1 sequential/test-net-GH-5504
# SERVER 2>NET 2664: listen2 null 12346 4 false undefined
# SERVER 2>NET 2664: _listen2: create a handle
# SERVER 2>NET 2664: bind to ::
# CLIENT 2>NET 2036: createConnection [ { host: 'localhost', port: 12346 }, [Function] ]
# CLIENT 2>NET 2036: pipe false undefined
# CLIENT 2>NET 2036: connect: find host localhost
# CLIENT 2>NET 2036: connect: dns options { family: undefined, hints: 1024 }
# C:\workspace\node-stress-single-test\nodes\win2008r2-1p\test\sequential\test-net-GH-5504.js:66
#       throw new Error('hang');
#       ^
# 
# Error: hang
#     at Timeout._onTimeout (C:\workspace\node-stress-single-test\nodes\win2008r2-1p\test\sequential\test-net-GH-5504.js:66:13)
#     at tryOnTimeout (timers.js:224:11)
#     at Timer.listOnTimeout (timers.js:198:5)
# SERVER 1>listening
  ---
  duration_ms: 3.204

@bnoordhuis
Copy link
Member

Possibly a transient DNS issue. win2008r2-1p stress test with bnoordhuis/io.js@284e2dc applied:
https://ci.nodejs.org/job/node-stress-single-test/781/

@Trott
Copy link
Member Author

Trott commented Jul 2, 2016

LGTM. :shipit:

bnoordhuis added a commit to bnoordhuis/io.js that referenced this issue Jul 4, 2016
Avoid transient DNS issues in test sequential/test-net-GH-5504 by using
the IP address instead of the 'localhost' host name.

Fixes: nodejs#6611
PR-URL: nodejs#7524
Reviewed-By: Brian White <mscdex@mscdex.net>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com>
Fishrock123 pushed a commit that referenced this issue Jul 5, 2016
Avoid transient DNS issues in test sequential/test-net-GH-5504 by using
the IP address instead of the 'localhost' host name.

Fixes: #6611
PR-URL: #7524
Reviewed-By: Brian White <mscdex@mscdex.net>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com>
MylesBorins pushed a commit that referenced this issue Jul 11, 2016
Avoid transient DNS issues in test sequential/test-net-GH-5504 by using
the IP address instead of the 'localhost' host name.

Fixes: #6611
PR-URL: #7524
Reviewed-By: Brian White <mscdex@mscdex.net>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com>
MylesBorins pushed a commit that referenced this issue Jul 12, 2016
Avoid transient DNS issues in test sequential/test-net-GH-5504 by using
the IP address instead of the 'localhost' host name.

Fixes: #6611
PR-URL: #7524
Reviewed-By: Brian White <mscdex@mscdex.net>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com>
MylesBorins pushed a commit that referenced this issue Jul 12, 2016
Avoid transient DNS issues in test sequential/test-net-GH-5504 by using
the IP address instead of the 'localhost' host name.

Fixes: #6611
PR-URL: #7524
Reviewed-By: Brian White <mscdex@mscdex.net>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com>
MylesBorins pushed a commit that referenced this issue Jul 14, 2016
Avoid transient DNS issues in test sequential/test-net-GH-5504 by using
the IP address instead of the 'localhost' host name.

Fixes: #6611
PR-URL: #7524
Reviewed-By: Brian White <mscdex@mscdex.net>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com>
MylesBorins pushed a commit that referenced this issue Jul 14, 2016
Avoid transient DNS issues in test sequential/test-net-GH-5504 by using
the IP address instead of the 'localhost' host name.

Fixes: #6611
PR-URL: #7524
Reviewed-By: Brian White <mscdex@mscdex.net>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
net Issues and PRs related to the net subsystem. test Issues and PRs related to the tests. windows Issues and PRs related to the Windows platform.
Projects
None yet
Development

No branches or pull requests

4 participants