Investigate flaky test-https-agent-create-connection on multiple platforms #11644

Activity

1. Trott

   added

   httpsIssues and PRs related to the https subsystem.Issues and PRs related to the https subsystem.

   testIssues and PRs related to Node.js core tests and test infrastructure.Issues and PRs related to Node.js core tests and test infrastructure.

   on Mar 2, 2017
2. mscdex commented on Mar 2, 2017

   

   mscdex

   on Mar 2, 2017

   Contributor

   More actions

   FWIW I just saw this same test fail, but with different output on the same rhel72-s390x machine:

   not ok 637 parallel/test-https-agent-create-connection
     ---
     duration_ms: 0.170
     severity: fail
     stack: |-
       
       assert.js:81
         throw new assert.AssertionError({
         ^
       AssertionError: false == true
           at TLSSocket.socket.on.common.mustCall (/data/iojs/build/workspace/node-test-commit-linuxone/nodes/rhel72-s390x/test/parallel/test-https-agent-create-connection.js:111:5)
           at TLSSocket.<anonymous> (/data/iojs/build/workspace/node-test-commit-linuxone/nodes/rhel72-s390x/test/common.js:452:15)
           at emitOne (events.js:96:13)
           at TLSSocket.emit (events.js:191:7)
           at emitErrorNT (net.js:1280:8)
           at _combinedTickCallback (internal/process/next_tick.js:80:11)
           at process._tickCallback (internal/process/next_tick.js:104:9)
   
3. mscdex commented on Mar 2, 2017

   

   mscdex

   on Mar 2, 2017

   Contributor

   More actions

   I should also add that the same stack trace I just posted for the same test has happened on centos5-32 now.
4. Trott

   changed the title [-]Investigate flaky test-https-agent-create-connection on LinuxONE[/-] [+]Investigate flaky test-https-agent-create-connection on multiple platforms[/+] on Mar 2, 2017
5. Trott commented on Mar 2, 2017

   

   Trott

   on Mar 2, 2017

   MemberAuthor

   More actions

   Now Windows: https://ci.nodejs.org/job/node-test-binary-windows/6823/RUN_SUBSET=3,VS_VERSION=vs2015,label=win2008r2/console

   not ok 160 parallel/test-https-agent-create-connection 
    ---
     duration_ms: 1.398
     severity: fail
     stack: |-
       events.js:163
             throw er; // Unhandled 'error' event
             ^
       
       Error: connect ECONNREFUSED 127.0.0.1:52212
           at Object.exports._errnoException (util.js:986:11)
           at exports._exceptionWithHostPort (util.js:1009:20)
           at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1089:14)
6. Trott commented on Mar 2, 2017

   

   Trott

   on Mar 2, 2017

   MemberAuthor

   More actions

   This is a brand new test as of about two weeks ago. Looping in author, approvers, and testing working group:

   @chiiia12 @jasnell @abouthiroppy @nodejs/testing
7. santigimeno commented on Mar 2, 2017

   

   santigimeno

   on Mar 2, 2017

   Member

   More actions

   @Trott, proposed fix here: #11649

   👍React with 👍1Reacted by Rich Trott

   🎉React with 🎉1Reacted by Rich Trott

   ❤️React with ❤️1Reacted by Rich Trott
8. santigimeno

   added a commit that references this issue on Mar 2, 2017

   test: fix flaky test-https-agent-create-connection

   ...

   5269e95
9. santigimeno

   closed this as completedin #11649on Mar 2, 2017
10. addaleax

    added a commit that references this issue on Mar 5, 2017

    test: fix flaky test-https-agent-create-connection

    ...

    00dd20c
11. MylesBorins

    added 2 commits that reference this issue on Apr 17, 2017

    test: fix flaky test-https-agent-create-connection

    ...

    577eb81

    test: fix flaky test-https-agent-create-connection

    ...

    640b72e
12. andrew749

    added a commit that references this issue on Jul 19, 2017

    test: fix flaky test-https-agent-create-connection

    ...

    fd5f0c7