Skip to content

test-cluster-message crash in CI #20201

Closed
Closed
test-cluster-message crash in CI#20201
Labels
buildIssues and PRs related to Node.js builds or CI infrastructure.clusterIssues and PRs related to the cluster subsystem.flaky-testIssues and PRs involving tests that fail intermittently in CI.testIssues and PRs related to Node.js core tests and test infrastructure.

Description

@Trott
Trott
opened on Apr 21, 2018
  • Version: v10.0.0-pre (master)
  • Platform: debian8-64
  • Subsystem: test build cluster

Not sure if there's anything that can be done about this but test-cluster-message crashed in CI on debian8-64:

https://ci.nodejs.org/job/node-test-commit-linux/18165/nodes=debian8-64/consoleText

not ok 223 parallel/test-cluster-message
  ---
  duration_ms: 0.510
  severity: crashed
  exitcode: -6
  stack: |-
    oh no!
    exit code: CRASHED (Signal: 6)
  ...

@nodejs/build

Activity

  1. Trott
    added
    clusterIssues and PRs related to the cluster subsystem.
    buildIssues and PRs related to Node.js builds or CI infrastructure.
    testIssues and PRs related to Node.js core tests and test infrastructure.
    flaky-testIssues and PRs involving tests that fail intermittently in CI.
    on Apr 21, 2018

  2. Trott commented on Apr 21, 2018

    @Trott
    Trott
    on Apr 21, 2018
    MemberAuthor

    Here's a crash on the same platform on a different test.

    https://ci.nodejs.org/job/node-test-commit-linux/18162/nodes=debian8-64/console

    00:16:04 not ok 2094 sequential/test-inspector-break-e
00:16:04   ---
00:16:04   duration_ms: 0.413
00:16:04   severity: crashed
00:16:04   exitcode: -6
00:16:04   stack: |-
00:16:04     oh no!
00:16:04     exit code: CRASHED (Signal: 6)

  3. Trott commented on Apr 21, 2018

    @Trott
    Trott
    on Apr 21, 2018
    MemberAuthor

    Both crashes were on test-digitalocean-debian8-x64-1 although I don't know if that's significant because I don't know that there are any other debian8-64 hosts.

  4. apapirovski commented on Apr 22, 2018

    @apapirovski
    apapirovski
    on Apr 22, 2018
    Contributor

    This is the same root cause as #19903 and will be fixed by #20129. I'll close this out since we have a tracking issue already.

  5. apapirovski
    closed this as completedon Apr 22, 2018
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

    buildIssues and PRs related to Node.js builds or CI infrastructure.clusterIssues and PRs related to the cluster subsystem.flaky-testIssues and PRs involving tests that fail intermittently in CI.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