Investigate flaky test-net-socket-timeout-unref

[Trott]

Example failure:

• pi2-raspbian-wheezy

[santigimeno]

@Trott Can you copy the output, please?

[Trott]

@santigimeno It's a timeout with no output from the test itself:

not ok 86 test-net-socket-timeout-unref.js
# TIMEOUT

[Trott]

Stress test: https://ci.nodejs.org/job/node-stress-single-test/549/nodes=pi2-raspbian-wheezy/console

[Trott]

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]

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]

Another one from today: https://ci.nodejs.org/job/node-test-binary-arm/1553/RUN_SUBSET=0,nodes=pi2-raspbian-wheezy/console

[santigimeno]

Of course adding the logging "fixes" the problem.

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]

Nah it's only the const, disregard it

[Trott]

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

[Trott]

Proposed fix: #6003