-
Notifications
You must be signed in to change notification settings - Fork 29.9k
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 parallel/test-process-getactivehandles #5302
Comments
/cc @trevnorris |
orangemocha
added a commit
that referenced
this issue
Feb 19, 2016
Ref: #5302 PR-URL: #5303 Reviewed-By: Rich Trott <[email protected]>
rvagg
pushed a commit
that referenced
this issue
Feb 21, 2016
Ref: #5302 PR-URL: #5303 Reviewed-By: Rich Trott <[email protected]>
More pi2 fun. |
how often is this flakey? I've been trying it out on a pi2 machine and hasn't failed for me. |
In the CI run (https://ci.nodejs.org/job/node-stress-single-test/504/nodes=pi2-raspbian-wheezy/console) it failed 2 times out of 100. We can start a longer run if you need more data. |
May have a fix for this. Will PR it soon. |
Linked a fix for the test. |
trevnorris
added a commit
to trevnorris/node
that referenced
this issue
Mar 3, 2016
Looping rapidly and making new connections causes problems on pi2. Instead create a new connection when an old connection has already been made. Running a stress test of 600 times and they all passed. Fixes: nodejs#5302 PR-URL: nodejs#5537 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Alexis Campailla <[email protected]>
Fishrock123
pushed a commit
that referenced
this issue
Mar 8, 2016
Looping rapidly and making new connections causes problems on pi2. Instead create a new connection when an old connection has already been made. Running a stress test of 600 times and they all passed. Fixes: #5302 PR-URL: #5537 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Alexis Campailla <[email protected]>
Fishrock123
pushed a commit
that referenced
this issue
Mar 8, 2016
Looping rapidly and making new connections causes problems on pi2. Instead create a new connection when an old connection has already been made. Running a stress test of 600 times and they all passed. Fixes: #5302 PR-URL: #5537 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Alexis Campailla <[email protected]>
MylesBorins
pushed a commit
that referenced
this issue
Mar 17, 2016
Looping rapidly and making new connections causes problems on pi2. Instead create a new connection when an old connection has already been made. Running a stress test of 600 times and they all passed. Fixes: #5302 PR-URL: #5537 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Alexis Campailla <[email protected]>
MylesBorins
pushed a commit
that referenced
this issue
Mar 21, 2016
Looping rapidly and making new connections causes problems on pi2. Instead create a new connection when an old connection has already been made. Running a stress test of 600 times and they all passed. Fixes: #5302 PR-URL: #5537 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Alexis Campailla <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Flaky on ARM on current master:
https://ci.nodejs.org/job/node-stress-single-test/504/nodes=pi2-raspbian-wheezy/console
cc @nodejs/testing
The text was updated successfully, but these errors were encountered: