Investigate flaky test-net-connect-reset-until-connected

[lpinca]

Test

test-net-connect-reset-until-connected

Platform

smartos

Console output

not ok 2579 parallel/test-net-connect-reset-until-connected
  ---
  duration_ms: 120.177
  severity: fail
  exitcode: -15
  stack: |-
    timeout

Build links

• https://ci.nodejs.org/job/node-test-commit-smartos/43640/
• https://ci.nodejs.org/job/node-test-commit-smartos/43655/

Additional information

No response

[panva]

Seems to have gone on strike June 9th, only on smartos20-64

https://ci.nodejs.org/job/node-test-commit-smartos/nodes=smartos20-64/buildTimeTrend

[panva]

Unfortunately doesn't seem to be just test-net-connect-reset-until-connected, i'm observing a tendency to timeout test-report-fatal-error, and test-domain-no-error-handler-abort-on-uncaught-* too on smartos20-64

[lpinca]

Yes, some other tests are also timing out. I think there is something wrong with that machine/system. @nodejs/build is it possible to restart it?

[panva]

ping @nodejs/build this build continues to be a problem

[Trott]

I saw this test failing over and over in #43366 so rebased against the main branch to see if it fixed it, and it did (based on a single run anyway). So maybe try that if all else fails?

[PupilTong]

Not sure if there is something wrong in #43112 since the server side RST test test/parallel/test-net-server-reset.js works.

Recent days I'm waiting the ISP starts my services plan. I will investigate the root casuse once my internet service is back (Expected Jul 4.).

:D

[F3n67u]

This test is also flaky on freebsd, could I mark it as flaky on freebsd also?

Reason	parallel/test-net-connect-reset-until-connected
Type	JS_TEST_FAILURE
Failed PR	5 (#42929, #43427, #43544, #43554, #43561)
Appeared	test-digitalocean-freebsd12-x64-2, test-digitalocean-freebsd12-x64-1
First CI	https://ci.nodejs.org/job/node-test-pull-request/44833/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/44876/

Details

not ok 2139 parallel/test-net-connect-reset-until-connected

duration_ms: 120.81
severity: fail
exitcode: -15
stack: |-
timeout
...

Refs: https://github.com/nodejs/reliability/issues/314