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

test-http2-session-timeout flaky on FreeBSD #15326

Description

@MylesBorins

This has been showing up a couple times in the v8.5.0-proposal testing

not ok 854 parallel/test-http2-session-timeout
  ---
  duration_ms: 0.957
  severity: fail
  stack: |-
    (node:89251) ExperimentalWarning: The http2 module is an experimental API.
    assert.js:41
      throw new errors.AssertionError({
      ^
    
    AssertionError [ERR_ASSERTION]: function should not have been called
        at Http2Server.mustNotCall (/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd10-64/test/common/index.js:560:12)
        at emitOne (events.js:115:13)
        at Http2Server.emit (events.js:210:7)
        at process.nextTick (internal/http2/core.js:2282:17)
        at _combinedTickCallback (internal/process/next_tick.js:131:7)
        at process._tickCallback (internal/process/next_tick.js:180:9)
  ...
ok 855 

/cc @nodejs/platform-freebsd

Activity

  1. MylesBorins commented on Sep 11, 2017

    @MylesBorins
    ContributorAuthor

    Digging into the test it would appear that this is a timout

    server.on('timeout', common.mustNotCall());

  2. BridgeAR commented on Sep 11, 2017

    @BridgeAR
    Member
  3. added
    freebsdIssues and PRs related to the FreeBSD platform.
    http2Issues and PRs related to the http2 subsystem.
    testIssues and PRs related to Node.js core tests and test infrastructure.
    on Sep 11, 2017
  4. Trott commented on Sep 11, 2017

    @Trott
    Member

    I am able to reproduce this trivially with:

    tools/test.py -j 96 --repeat 192 test/parallel/test-http2-session-timeout.js
    

    (Note that at this time you need to apply the patch from #15300 or back out c8a389e to use the test runner like that.)

  5. Trott commented on Sep 11, 2017

    @Trott
    Member

    This is not FreeBSD-specific. The test is just straight-up not tolerant of concurrency. Removing the freebsd label.

  6. added
    flaky-testIssues and PRs involving tests that fail intermittently in CI.
    and removed
    freebsdIssues and PRs related to the FreeBSD platform.
    on Sep 11, 2017
  7. Trott commented on Sep 11, 2017

    @Trott
    Member

    Aside: This test uses the .timeout property of the Http2Server class but that property (and all properties on that class) is undocumented. @nodejs/http2 @nodejs/documentation

  8. Trott commented on Sep 11, 2017

    @Trott
    Member

    Simplest solution is to bump up serverTimeout. Changing it to 1200 (which is exactly 1/100 of the default value) allows me to run 96 simultaneous copies of the test locally reliably. Previously, I was getting errors sometimes with as few as 8 or 16 concurrent tests, and reliably with 32 concurrent tests.

    PR coming momentarily.

  9. Trott commented on Sep 11, 2017

    @Trott
    Member

    Fix (or at least mitigation) is in #15328

  10. apapirovski commented on Sep 14, 2017

    @apapirovski
    Contributor

    Sorry, everyone. We're trying to get this nailed down. If someone wants to start a stress test for the latest commit apapirovski@3103f89 that would be appreciated!

    Edit: Sorry, this is the PR #15338

  11. Trott commented on Sep 14, 2017

    @Trott
    Member

    If someone wants to start a stress test

    I'm on it.

  12. Trott commented on Sep 16, 2017

    @Trott
    Member

    Still failing on FreeBSD with some frequency.Example: https://ci.nodejs.org/job/node-test-commit-freebsd/11602/nodes=freebsd10-64/console

    I'll open a PR to move it to sequential as-is (to get it working right away) and it can be moved back in #15338 whenever that lands.

  13. added a commit that references this issue on Sep 16, 2017
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

    flaky-testIssues and PRs involving tests that fail intermittently in CI.http2Issues and PRs related to the http2 subsystem.testIssues and PRs related to Node.js core tests and test infrastructure.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions