镜像站点 · 本页由第三方 GitHub 只读镜像提供，非 GitHub 官方站点，不接受任何登录或凭据输入。前往 github.com
Skip to content

test-https-set-timeout-server on freebsd #10130

Closed
Closed
test-https-set-timeout-server on freebsd#10130
Labels
freebsdIssues and PRs related to the FreeBSD platform.httpsIssues and PRs related to the https subsystem.testIssues and PRs related to Node.js core tests and test infrastructure.timersIssues and PRs related to timers, setImmediate(), setInterval(), and setTimeout().

Description

@mhdawson
mhdawson
opened on Dec 5, 2016
  • Version: master
  • Platform: freebsd10-64
  • Subsystem:https

Failure seen when running test against a PR changing a different test:

https://ci.nodejs.org/job/node-test-commit-freebsd/5673/nodes=freebsd10-64/

not ok 614 parallel/test-https-set-timeout-server
  ---
  duration_ms: 1.645
  severity: fail
  stack: |-
    # serverTimeout
    # serverRequestTimeout
    # serverResponseTimeout
    # serverRequestNotTimeoutAfterEnd
    # serverResponseTimeoutWithPipeline
    # idleTimeout
    ok
    Mismatched <anonymous> function calls. Expected 1, actual 0.
        at idleTimeout (/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd10-64/test/parallel/test-https-set-timeout-server.js:149:42)
        at run (/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd10-64/test/parallel/test-https-set-timeout-server.js:31:5)
        at Server.<anonymous> (/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd10-64/test/parallel/test-https-set-timeout-server.js:131:5)
        at emitOne (events.js:96:13)
        at Server.emit (events.js:188:7)
        at TLSSocket.<anonymous> (_http_server.js:314:30)
        at emitNone (events.js:86:13)
        at TLSSocket.emit (events.js:185:7)
        at TLSSocket.Socket._onTimeout (net.js:342:8)
  ...

Activity

  1. mhdawson
    added
    testIssues and PRs related to Node.js core tests and test infrastructure.
    on Dec 5, 2016

  2. mhdawson commented on Dec 5, 2016

    @mhdawson
    mhdawson
    on Dec 5, 2016
    MemberAuthor

    Looking at history don't see any recent changes to the test.

  3. mscdex
    added
    freebsdIssues and PRs related to the FreeBSD platform.
    httpsIssues and PRs related to the https subsystem.
    timersIssues and PRs related to timers, setImmediate(), setInterval(), and setTimeout().
    on Dec 5, 2016

  4. mhdawson commented on Dec 5, 2016

    @mhdawson
    mhdawson
    on Dec 5, 2016
    MemberAuthor

    Failed again here: https://ci.nodejs.org/job/node-test-commit-freebsd/5675/nodes=freebsd10-64/console

  5. Trott commented on Dec 7, 2016

    @Trott
    Trott
    on Dec 7, 2016
    Member

    Giving it a quick look, moving to sequential will probably make it more reliable. /cc @nodejs/testing

  6. Trott commented on Apr 27, 2017

    @Trott
    Trott
    on Apr 27, 2017
    Member

    Failed again today. https://ci.nodejs.org/job/node-test-commit-freebsd/8596/nodes=freebsd10-64/console

    not ok 664 parallel/test-https-set-timeout-server
  ---
  duration_ms: 1.263
  severity: fail
  stack: |-
    # serverTimeout
    # serverRequestTimeout
    # serverResponseTimeout
    # serverRequestNotTimeoutAfterEnd
    # serverResponseTimeoutWithPipeline
    # idleTimeout
    ok
    Mismatched <anonymous> function calls. Expected 1, actual 0.
        at idleTimeout (/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd10-64/test/parallel/test-https-set-timeout-server.js:170:44)
        at run (/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd10-64/test/parallel/test-https-set-timeout-server.js:52:5)
        at Server.<anonymous> (/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd10-64/test/parallel/test-https-set-timeout-server.js:152:5)
        at emitOne (events.js:115:13)
        at Server.emit (events.js:210:7)
        at TLSSocket.socketOnTimeout (_http_server.js:385:35)
        at emitNone (events.js:105:13)
        at TLSSocket.emit (events.js:207:7)
        at TLSSocket.Socket._onTimeout (net.js:374:8)

  7. Trott commented on Apr 27, 2017

    @Trott
    Trott
    on Apr 27, 2017
    Member

    I'm going to run some stress tests on it in parallel vs. sequential and see what happens.

  8. Trott commented on Apr 27, 2017

    @Trott
    Trott
    on Apr 27, 2017
    Member

    CI stress test on freebsd10-64 with -j 4 --repeat=4:

    https://ci.nodejs.org/job/node-stress-single-test/1175/nodes=freebsd10-64/console

  9. Trott commented on Apr 27, 2017

    @Trott
    Trott
    on Apr 27, 2017
    Member

    Ci stress test on freebsd10-64 with -j 8 --repeat=8:

    https://ci.nodejs.org/job/node-stress-single-test/1176/nodes=freebsd10-64/console

  10. Trott commented on Apr 27, 2017

    @Trott
    Trott
    on Apr 27, 2017
    Member

    8 seems to be enough to cause failures identical to what we're seeing in CI from time to time, so that's good. But the errors are infrequent. (I got 1 in 500 runs.) Trying 16 to see if we can get failures to happen with greater frequency:

    https://ci.nodejs.org/job/node-stress-single-test/1177/nodes=freebsd10-64/console

    That gives me 92 failures out of 100 runs. Cool. Solution is certainly to move it to sequential but I'll run a stress test on that anyway.

  11. Trott commented on Apr 27, 2017

    @Trott
    Trott
    on Apr 27, 2017
    Member

    Actually, I wonder if moving the setting of the server timeout to the callback might be the solution...

  12. Trott
    closed this as completedin 0833d31on Apr 30, 2017
  13. gibfahn
    added a commit that references this issue on May 15, 2017

    test: move test to sequential for reliability

    c1e4b2f
  14. andrew749
    added a commit that references this issue on Jul 19, 2017

    test: move test to sequential for reliability

    873451b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    freebsdIssues and PRs related to the FreeBSD platform.httpsIssues and PRs related to the https subsystem.testIssues and PRs related to Node.js core tests and test infrastructure.timersIssues and PRs related to timers, setImmediate(), setInterval(), and setTimeout().

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions