Example failure: - [pi2-raspbian-wheezy](https://ci.nodejs.org/job/node-test-binary-arm/988/RUN_SUBSET=0,nodes=pi2-raspbian-wheezy/tapTestReport/test.tap-86/)
Activity
santigimeno commentedon Feb 7, 2016
@Trott Can you copy the output, please?
Trott commentedon Feb 7, 2016
@santigimeno It's a timeout with no output from the test itself:
Trott commentedon Feb 28, 2016
Stress test: https://ci.nodejs.org/job/node-stress-single-test/549/nodes=pi2-raspbian-wheezy/console
Trott commentedon Mar 28, 2016
Another instance from today. No new info, just documenting that it is still happening two-ish months later... :-/ https://ci.nodejs.org/job/node-test-binary-arm/1509/RUN_SUBSET=5,nodes=pi2-raspbian-wheezy/console
Trott commentedon Mar 29, 2016
Created a branch and added a little logging in the hopes of finding out what's going on that's causing it to hang sometimes on pi2-raspbian-wheezy. Now running stress test for it: https://ci.nodejs.org/job/node-stress-single-test/575/nodes=pi2-raspbian-wheezy/console UPDATE: Of course adding the logging "fixes" the problem. Meh.
Trott commentedon Apr 1, 2016
Another one from today: https://ci.nodejs.org/job/node-test-binary-arm/1553/RUN_SUBSET=0,nodes=pi2-raspbian-wheezy/console
santigimeno commentedon Apr 1, 2016
Highly unlikely, but maybe the refactoring to use newer syntax did something.
Maybe it's worth it launching the stress test again only with the logs.
santigimeno commentedon Apr 1, 2016
Nah it's only the
const, disregard itTrott commentedon Apr 1, 2016
I think I have a fix for this... Stress test is 275 successful runs and counting: https://ci.nodejs.org/job/node-stress-single-test/583/nodes=pi2-raspbian-wheezy/console
test: fix flaky test-net-socket-timeout-unref
Trott commentedon Apr 1, 2016
Proposed fix: #6003
test: fix flaky test-net-socket-timeout-unref
test: fix flaky test-net-socket-timeout-unref
test: fix flaky test-net-socket-timeout-unref