flaky: test-net-connect-options-port #23207

Activity

1. refack

   added

   netIssues and PRs related to the net subsystem.Issues and PRs related to the net subsystem.

   flaky-testIssues and PRs involving tests that fail intermittently in CI.Issues and PRs involving tests that fail intermittently in CI.

   on Oct 1, 2018
2. Trott commented on Oct 7, 2018

   

   Trott

   on Oct 7, 2018

   Member

   More actions

   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   ...
3. Trott commented on Oct 7, 2018

   

   Trott

   on Oct 7, 2018

   Member

   More actions

   Stress test: https://ci.nodejs.org/job/node-stress-single-test/2064/
4. refack commented on Oct 7, 2018

   

   refack

   on Oct 7, 2018

   ContributorAuthor

   More actions

   fails in ci.nodejs.org/job/node-stress-single-test/2064
   alpine-last-latest-x64 - 29 in 1600
   win2008r2-mp-vs2017 - 4 in 1600
5. Trott commented on Oct 8, 2018

   

   Trott

   on Oct 8, 2018

   Last edited by Trott

   Member

   More actions

   Parameters for stress test were:

   RUN_TESTS: -j 8 --repeat 16 parallel/test-net-connect-options-port
   RUN_TIMES: 100
6. Trott commented on Oct 11, 2018

   

   Trott

   on Oct 11, 2018

   Member

   More actions

   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/
7. Trott commented on Jun 14, 2019

   

   Trott

   on Jun 14, 2019

   Member

   More actions

   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.
8. BridgeAR commented on Feb 14, 2020

   

   BridgeAR

   on Feb 14, 2020

   Member

   More actions

   Just checking if this is still flaky: https://ci.nodejs.org/job/node-stress-single-test/61/
9. Trott commented on Feb 18, 2020

   

   Trott

   on Feb 18, 2020

   Member

   More actions

   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.
10. Trott commented on Feb 18, 2020

    

    Trott

    on Feb 18, 2020

    Member

    More actions

    #31841
11. Trott

    added a commit that references this issue on Feb 20, 2020

    test: remove flaky designation for test-net-connect-options-port

    ...

    cdac185
12. Trott

    closed this as completedin cdac185on Feb 20, 2020
13. codebytere

    added a commit that references this issue on Feb 27, 2020

    test: remove flaky designation for test-net-connect-options-port

    ...

    7d5776e
14. codebytere

    added 2 commits that reference this issue on Mar 15, 2020

    test: remove flaky designation for test-net-connect-options-port

    ...

    86cd207

    test: remove flaky designation for test-net-connect-options-port

    ...

    58b2f86
15. codebytere

    added a commit that references this issue on Mar 30, 2020

    test: remove flaky designation for test-net-connect-options-port

    ...

    bde5a9b