CI Reliability 2022-12-08

Open
#451 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
node.js, shell
Domain
ci-cd, devops, testing

Research direction

Start with the generated ncu-ci walk pr report and review the linked Jenkins runs for the listed BUILD_FAILURE, JENKINS_FAILURE, and JS_TEST_FAILURE entries. Use the named tests such as parallel/test-fs-watch-recursive and parallel/test-process-wrap as investigation entry points; the issue does not define a specific code change or completion condition.

Written by the indexing model from the issue text.

Description

Failures in node-test-pull-request/48237 to node-test-pull-request/48330 that failed more than 2 PRs
(Generated with ncu-ci walk pr --stats=true --markdown /home/runner/work/reliability/reliability/results.md)

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2022-12-08 00:13 5 5 21 13 56 6.10%
CCTest Failure
Jenkins Failure
Reason Backing channel 'JNLP4-connect connection from ... is disconnected.
Type JENKINS_FAILURE
Failed PR 4 (https://github.com/nodejs/node/pull/45682/, https://github.com/nodejs/node/pull/45716/, https://github.com/nodejs/node/pull/45705/, https://github.com/nodejs/node/pull/45744/)
Appeared test-digitalocean-freebsd12-x64-2, test-digitalocean-freebsd12-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/48240/
Last CI https://ci.nodejs.org/job/node-test-pull-request/48316/
Example
java.io.IOException: Backing channel 'JNLP4-connect connection from 107.170.28.213/107.170.28.213:10157' is disconnected.
	at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:215)
	at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:285)
	at jdk.proxy2/jdk.proxy2.$Proxy82.isAlive(Unknown Source)
	at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1215)
	at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1207)

Git Failure
Build Failure
Reason Failed to trigger node-test-commit
Type BUILD_FAILURE
Failed PR 11 (https://github.com/nodejs/node/pull/45674/, https://github.com/nodejs/node/pull/45735/, https://github.com/nodejs/node/pull/45745/, https://github.com/nodejs/node/pull/45744/, https://github.com/nodejs/node/pull/45401/, https://github.com/nodejs/node/pull/45733/, https://github.com/nodejs/node/pull/45750/, https://github.com/nodejs/node/pull/45749/, https://github.com/nodejs/node/pull/45748/, https://github.com/nodejs/node/pull/45747/, https://github.com/nodejs/node/pull/45701/)
Appeared test-equinix-ubuntu2204-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/48292/
Last CI https://ci.nodejs.org/job/node-test-pull-request/48303/
Example
Failed to trigger node-test-commit

JSTest Failure
Reason parallel/test-fs-watch-recursive
Type JS_TEST_FAILURE
Failed PR 16 (https://github.com/nodejs/node/pull/45486/, https://github.com/nodejs/node/pull/45634/, https://github.com/nodejs/node/pull/45672/, https://github.com/nodejs/node/pull/45671/, https://github.com/nodejs/node/pull/45526/, https://github.com/nodejs/node/pull/45693/, https://github.com/nodejs/node/pull/43697/, https://github.com/nodejs/node/pull/45665/, https://github.com/nodejs/node/pull/45705/, https://github.com/nodejs/node/pull/45673/, https://github.com/nodejs/node/pull/45731/, https://github.com/nodejs/node/pull/45701/, https://github.com/nodejs/node/pull/45748/, https://github.com/nodejs/node/pull/45767/, https://github.com/nodejs/node/pull/45765/, https://github.com/nodejs/node/pull/45770/)
Appeared test-orka-macos11-x64-1, test-digitalocean-ubuntu1804_sharedlibs_container-x64-2, test-digitalocean-ubuntu1804_sharedlibs_container-x64-4, test-osuosl-rhel8-ppc64_le-2, test-digitalocean-ubuntu1804_sharedlibs_container-x64-9, test-nearform-macos11.0-arm64-1, test-ibm-rhel8-s390x-4, test-macstadium-macos11.0-arm64-3, test-orka-macos11-x64-2, test-digitalocean-alpine311_container-x64-2, test-digitalocean-ubi81_container-x64-2, test-softlayer-ubuntu1804_sharedlibs_container-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/48237/
Last CI https://ci.nodejs.org/job/node-test-pull-request/48330/
Example
not ok 1240 parallel/test-fs-watch-recursive
  ---
  duration_ms: 120.62
  severity: fail
  exitcode: -15
  stack: |-
    timeout
    (node:30459) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 exit listeners added to [process]. Use emitter.setMaxListeners() to increase limit
    (Use `node --trace-warnings ...` to show where the warning was created)
  ...


Reason parallel/test-process-wrap
Type JS_TEST_FAILURE
Failed PR 9 (https://github.com/nodejs/node/pull/45526/, https://github.com/nodejs/node/pull/45672/, https://github.com/nodejs/node/pull/45665/, https://github.com/nodejs/node/pull/45745/, https://github.com/nodejs/node/pull/45701/, https://github.com/nodejs/node/pull/45746/, https://github.com/nodejs/node/pull/45744/, https://github.com/nodejs/node/pull/45767/, https://github.com/nodejs/node/pull/45674/)
Appeared test-nearform-macos10.15-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/48242/
Last CI https://ci.nodejs.org/job/node-test-pull-request/48326/
Example
not ok 2504 parallel/test-process-wrap
  ---
  duration_ms: 120.31
  severity: fail
  exitcode: -15
  stack: |-
    timeout
    (node:98808) internal/test/binding: These APIs are for internal testing only. Do not use them.
    (Use `node --trace-warnings ...` to show where the warning was created)
  ...


Reason parallel/test-child-process-stdio-inherit
Type JS_TEST_FAILURE
Failed PR 8 (https://github.com/nodejs/node/pull/45526/, https://github.com/nodejs/node/pull/43697/, https://github.com/nodejs/node/pull/45586/, https://github.com/nodejs/node/pull/45716/, https://github.com/nodejs/node/pull/45745/, https://github.com/nodejs/node/pull/45701/, https://github.com/nodejs/node/pull/45698/, https://github.com/nodejs/node/pull/45765/)
Appeared test-nearform-macos10.15-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/48249/
Last CI https://ci.nodejs.org/job/node-test-pull-request/48322/
Example
not ok 726 parallel/test-child-process-stdio-inherit
  ---
  duration_ms: 120.136
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason parallel/test-child-process-exec-timeout-kill
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/43697/, https://github.com/nodejs/node/pull/45770/)
Appeared test-digitalocean-freebsd12-x64-2, test-nearform-macos10.15-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/48257/
Last CI https://ci.nodejs.org/job/node-test-pull-request/48330/
Example
not ok 365 parallel/test-child-process-exec-timeout-kill
  ---
  duration_ms: 0.270
  severity: fail
  exitcode: 1
  stack: |-
    [stdout] 
    [stderr] 
    node:assert:124
      throw new AssertionError(obj);
      ^
    
    AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
    
    1 !== null
    
        at /usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd12-x64/test/parallel/test-child-process-exec-timeout-kill.js:32:10
        at /usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd12-x64/test/common/index.js:448:15
        at ChildProcess.exithandler (node:child_process:427:5)
        at ChildProcess.emit (node:events:511:28)
        at maybeClose (node:internal/child_process:1098:16)
        at Socket.<anonymous> (node:internal/child_process:456:11)
        at Socket.emit (node:events:511:28)
        at Pipe.<anonymous> (node:net:305:12) {
      generatedMessage: true,
      code: 'ERR_ASSERTION',
      actual: 1,
      expected: null,
      op...

Reason parallel/test-crypto-key-objects
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/44873/, https://github.com/nodejs/node/pull/45660/)
Appeared test-ibm-rhel7-s390x-4, test-joyent-ubuntu1804-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/48253/
Last CI https://ci.nodejs.org/job/node-test-pull-request/48323/
Example
not ok 2979 parallel/test-crypto-key-objects
  ---
  duration_ms: 120.58
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason parallel/test-runner-inspect
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/45671/, https://github.com/nodejs/node/pull/45665/)
Appeared test-nearform-macos10.15-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/48247/
Last CI https://ci.nodejs.org/job/node-test-pull-request/48263/
Example
not ok 2662 parallel/test-runner-inspect
  ---
  duration_ms: 120.66
  severity: fail
  exitcode: -15
  stack: |-
    timeout
    [test] Connecting to a child Node process
    [test] Testing /json/list
    [err] (node:50255) Warning: Using the inspector with --test forces running at a concurrency of 1. Use the inspectPort option to run with concurrency
    [err] (Use `node --trace-warnings ...` to show where the warning was created)
    [err] 
    [out] TAP version 13
    [out] 
    [err] Debugger listening on ws://127.0.0.1:50899/2678ba3b-c74a-468d-a90e-afd28d72676a
    [err] 
    [err] Debugger listening on ws://127.0.0.1:50899/2678ba3b-c74a-468d-a90e-afd28d72676a
    [err] 
    [out] # Subtest: /Users/iojs/build/workspace/node-test-commit-osx/nodes/osx1015/test/fixtures/test-runner/index.test.js
    [out] 
    [out]     # Debugger listening on ws://127.0.0.1:50899/2678ba3b-c74a-468d-a90e-afd28d72676a
    [out] 
    [out]     # For help, see: https://nodejs.org/en/docs/inspector
    [out] 
    [err] Debugge...

Progress
  • Backing channel 'JNLP4-connect connection from ... is disconnected. (4)
  • Failed to trigger node-test-commit (11)
  • parallel/test-fs-watch-recursive (16)
  • parallel/test-process-wrap (9)
  • parallel/test-child-process-stdio-inherit (8)
  • parallel/test-child-process-exec-timeout-kill (2)
  • parallel/test-crypto-key-objects (2)
  • parallel/test-runner-inspect (2)
Dominant language
Shell
Stars
57
Forks
20
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nodejs/reliability

All issues in nodejs/reliability

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.