flaky: test-net-connect-options-port

[refack]

https://ci.nodejs.org/job/node-test-commit-linux/nodes=alpine-last-latest-x64/22004/

timeout

https://ci.nodejs.org/job/node-test-commit-plinux/20584/

timeout

[Trott]

Also Windows:

https://ci.nodejs.org/job/node-test-binary-windows/20561/COMPILED_BY=vs2017,RUNNER=win2008r2-vs2017,RUN_SUBSET=1/console

02:28:41 not ok 327 parallel/test-net-connect-options-port # TODO : Fix flaky test
02:28:41   ---
02:28:41   duration_ms: 120.74
02:28:41   severity: fail
02:28:41   exitcode: 1
02:28:41   stack: |-
02:28:41     timeout
02:28:41   ...

[Trott]

Stress test: https://ci.nodejs.org/job/node-stress-single-test/2064/

[refack]

fails in ci.nodejs.org/job/node-stress-single-test/2064
alpine-last-latest-x64 - 29 in 1600
win2008r2-mp-vs2017 - 4 in 1600

[Trott]

Parameters for stress test were:

RUN_TESTS: -j 8 --repeat 16 parallel/test-net-connect-options-port
RUN_TIMES: 100

[Trott]

Running stress test again in case the libuv upgrade or something else might fix this:

https://ci.nodejs.org/job/node-stress-single-test/2066/

[Trott]

Running stress test again in case the libuv upgrade or something else might fix this:

https://ci.nodejs.org/job/node-stress-single-test/2066/

I'm guessing I forgot to circle back and check those results, and now they're long gone. But I haven't seen this in a while, I don't think, so let's see...

https://ci.nodejs.org/job/node-stress-single-test/2227/ (queued)

Parameters are as above.

[BridgeAR]

Just checking if this is still flaky: https://ci.nodejs.org/job/node-stress-single-test/61/

[Trott]

Just checking if this is still flaky: https://ci.nodejs.org/job/node-stress-single-test/61/

CI is green. Looks like we can unmark the test and close this issue.

[Trott]

#31841