CI Reliability 2022-12-16

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
node.js, shell

Research direction

Start with the linked Jenkins CI runs and the listed failures in test/parallel, test/pummel, and test/common. The report groups recurring failures such as test-fs-watch-recursive, test-child-process-exec-timeout-kill, and test-tls-ticket-cluster; done would require a concrete diagnosis and resolution for the relevant CI failures.

Written by the indexing model from the issue text.

Description

Failures in node-test-pull-request/48414 to node-test-pull-request/48474 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-16 00:12 25 3 15 16 41 5.08%
CCTest Failure
Jenkins Failure
Reason Backing channel 'JNLP4-connect connection from ... is disconnected.
Type JENKINS_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/45803/, https://github.com/nodejs/node/pull/45849/, https://github.com/nodejs/node/pull/45852/)
Appeared test-orka-macos11-x64-1, test-digitalocean-freebsd12-x64-1, test-digitalocean-freebsd12-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/48418/
Last CI https://ci.nodejs.org/job/node-test-pull-request/48473/
Example
java.io.IOException: Backing channel 'JNLP4-connect connection from 199.7.167.102/199.7.167.102:37249' 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)

Build Failure
Reason Error: getWindowSize EINVAL
Type BUILD_FAILURE
Failed PR 10 (https://github.com/nodejs/node/pull/45822/, https://github.com/nodejs/node/pull/45803/, https://github.com/nodejs/node/pull/45811/, https://github.com/nodejs/node/pull/45817/, https://github.com/nodejs/node/pull/45826/, https://github.com/nodejs/node/pull/45621/, https://github.com/nodejs/node/pull/45704/, https://github.com/nodejs/node/pull/45831/, https://github.com/nodejs/node/pull/45855/, https://github.com/nodejs/node/pull/45850/)
Appeared test-joyent-smartos18-x64-3, test-joyent-smartos20-x64-4, test-joyent-smartos20-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/48414/
Last CI https://ci.nodejs.org/job/node-test-pull-request/48474/
Example
Error: getWindowSize EINVAL
outline =     at WriteStream._refreshSize (tty.js:133:31)
outline =     at process.<anonymous> (internal/bootstrap/switches/is_main_thread.js:127:41)
outline =     at process.emit (events.js:400:28)
outline = Emitted 'error' event on WriteStream instance at:
outline =     at WriteStream._refreshSize (tty.js:133:10)

undefined
JSTest Failure
Reason parallel/test-fs-watch-recursive
Type JS_TEST_FAILURE
Failed PR 9 (https://github.com/nodejs/node/pull/45803/, https://github.com/nodejs/node/pull/45621/, https://github.com/nodejs/node/pull/45815/, https://github.com/nodejs/node/pull/45817/, https://github.com/nodejs/node/pull/45831/, https://github.com/nodejs/node/pull/45298/, https://github.com/nodejs/node/pull/45604/, https://github.com/nodejs/node/pull/45778/, https://github.com/nodejs/node/pull/45777/)
Appeared test-orka-macos11-x64-1, test-softlayer-ubuntu1804_sharedlibs_container-x64-1, test-nearform-macos11.0-arm64-1, test-osuosl-rhel8-ppc64_le-2, test-osuosl-rhel8-ppc64_le-1, test-digitalocean-ubuntu1804_sharedlibs_container-x64-9, test-osuosl-rhel8-ppc64_le-3, test-ibm-rhel8-s390x-4
First CI https://ci.nodejs.org/job/node-test-pull-request/48418/
Last CI https://ci.nodejs.org/job/node-test-pull-request/48467/
Example
not ok 1233 parallel/test-fs-watch-recursive
  ---
  duration_ms: 120.46
  severity: fail
  exitcode: -15
  stack: |-
    timeout
    (node:12328) 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-child-process-exec-timeout-kill
Type JS_TEST_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/45831/, https://github.com/nodejs/node/pull/45826/, https://github.com/nodejs/node/pull/45852/)
Appeared test-digitalocean-freebsd12-x64-1, test-digitalocean-freebsd12-x64-2, test-nearform-macos10.15-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/48432/
Last CI https://ci.nodejs.org/job/node-test-pull-request/48473/
Example
not ok 366 parallel/test-child-process-exec-timeout-kill
  ---
  duration_ms: 0.372
  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:519:28)
        at maybeClose (node:internal/child_process:1098:16)
        at ChildProcess._handle.onexit (node:internal/child_process:304:5) {
      generatedMessage: true,
      code: 'ERR_ASSERTION',
      actual: 1,
      expected: null,
      operator: 'strictEqual'
    }
    
    Node.js v20.0.0-pre
  ...


Reason parallel/test-tls-ticket-cluster
Type JS_TEST_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/45822/, https://github.com/nodejs/node/pull/45831/, https://github.com/nodejs/node/pull/45851/)
Appeared test-nearform_arm-win10_vs2019-arm64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/48414/
Last CI https://ci.nodejs.org/job/node-test-pull-request/48460/
Example
not ok 732 parallel/test-tls-ticket-cluster
  ---
  duration_ms: 1.80
  severity: fail
  exitcode: 1
  stack: |-
    [primary] got "listening"
    [primary] connecting 55737 session? false
    [primary] got "listening"
    [primary] got "listening"
    [worker] connection reused? false
    [primary] got "not-reused"
    [primary] connecting 55737 session? true
    [worker] connection reused? true
    [primary] got "reused"
    [primary] connecting 55737 session? true
    [worker] connection reused? true
    [primary] got "reused"
    [primary] connecting 55737 session? true
    [worker] connection reused? true
    [primary] got "reused"
    [primary] connecting 55737 session? true
    [worker] connection reused? true
    [primary] got "reused"
    [primary] connecting 55737 session? true
    [worker] connection reused? true
    [primary] got "reused"
    [primary] connecting 55737 session? true
    [worker] connection reused? true
    [primary] got "reused"
    [primary] connecting 55737 session? true
    [wo...

Reason pummel/test-net-throttle
Type JS_TEST_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/45831/, https://github.com/nodejs/node/pull/45851/, https://github.com/nodejs/node/pull/45852/)
Appeared test-digitalocean-freebsd12-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/48452/
Last CI https://ci.nodejs.org/job/node-test-pull-request/48461/
Example
not ok 3468 pummel/test-net-throttle
  ---
  duration_ms: 0.447
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:124
      throw new AssertionError(obj);
      ^
    
    AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
    
    false !== true
    
        at process.<anonymous> (/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd12-x64/test/pummel/test-net-throttle.js:87:10)
        at process.emit (node:events:531:35) {
      generatedMessage: true,
      code: 'ERR_ASSERTION',
      actual: false,
      expected: true,
      operator: 'strictEqual'
    }
    
    Node.js v20.0.0-pre
  ...


Reason pummel/test-fs-readfile-tostring-fail
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/45826/, https://github.com/nodejs/node/pull/45831/)
Appeared test-digitalocean-freebsd12-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/48447/
Last CI https://ci.nodejs.org/job/node-test-pull-request/48448/
Example
not ok 3438 pummel/test-fs-readfile-tostring-fail
  ---
  duration_ms: 40.759
  severity: fail
  exitcode: 7
  stack: |-
    /usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd12-x64/test/pummel/test-fs-readfile-tostring-fail.js:73
      throw err;
      ^
    
    AssertionError [ERR_ASSERTION]: 302907392 bytes written (expected 539555154 bytes).
        at WriteStream.<anonymous> (/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd12-x64/test/pummel/test-fs-readfile-tostring-fail.js:37:10)
        at WriteStream.<anonymous> (/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd12-x64/test/common/index.js:448:15)
        at WriteStream.emit (node:events:513:28)
        at finish (node:internal/streams/writable:750:10)
        at finishMaybe (node:internal/streams/writable:735:9)
        at afterWrite (node:internal/streams/writable:507:3)
        at onwrite (node:internal/streams/writable:480:7)
        at node:internal/fs/streams:443:5
        at FSReqCall...

Progress
  • Backing channel 'JNLP4-connect connection from ... is disconnected. (3)
  • Error: getWindowSize EINVAL (10)
  • parallel/test-fs-watch-recursive (9)
  • parallel/test-child-process-exec-timeout-kill (3)
  • parallel/test-tls-ticket-cluster (3)
  • pummel/test-net-throttle (3)
  • pummel/test-fs-readfile-tostring-fail (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.