CI Reliability 2023-11-07

Open
#710 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
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
git, shell

Research direction

Start with the linked Jenkins jobs and the generated ncu-ci report, grouping the repeated failures by reason and affected worker. The issue lists examples for Jenkins, Git, and build failures but names no repository files or tests. Done is not defined; clarify the intended remediation and success criteria for the recurring failures.

Written by the indexing model from the issue text.

Description

Failures in node-test-pull-request/55367 to node-test-pull-request/55463 that failed 2 or more 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
2023-11-07 00:13 0 3 31 3 63 3.09%
Jenkins Failure
Reason Backing channel 'JNLP4-connect connection from ... is disconnected.
Type JENKINS_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/50505/, https://github.com/nodejs/node/pull/50531/, https://github.com/nodejs/node/pull/50552/)
Appeared test-orka-macos11-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/55389/
Last CI https://ci.nodejs.org/job/node-test-pull-request/55443/
Example
java.io.IOException: Backing channel 'JNLP4-connect connection from 199.7.167.102/199.7.167.102:42511' is disconnected.
	at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:215)
	at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:285)
	at jdk.proxy2/jdk.proxy2.$Proxy166.isAlive(Unknown Source)
	at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1212)
	at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1204)

Reason Build timed out (after 120 minutes). Marking the build as failed.
Type JENKINS_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/50492/, https://github.com/nodejs/node/pull/50466/)
Appeared test-digitalocean-fedora32-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/55444/
Last CI https://ci.nodejs.org/job/node-test-pull-request/55453/
Example
Build timed out (after 120 minutes). Marking the build as failed.

Git Failure
Reason ERROR: Error fetching remote repo 'origin'
Type GIT_FAILURE
Failed PR 6 (https://github.com/nodejs/node/pull/50474/, https://github.com/nodejs/node/pull/49213/, https://github.com/nodejs/node/pull/50360/, https://github.com/nodejs/node/pull/50488/, https://github.com/nodejs/node/pull/50354/, https://github.com/nodejs/node/pull/50385/)
Appeared test-orka-macos11-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/55367/
Last CI https://ci.nodejs.org/job/node-test-pull-request/55427/
Example
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from git@github.com:nodejs/node.git
	at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:999)
	at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1241)
	at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1305)
	at hudson.scm.SCM.checkout(SCM.java:540)

Build Failure
Reason fatal error: string_view: No such file or directory
Type BUILD_FAILURE
Failed PR 14 (https://github.com/nodejs/node/pull/50488/, https://github.com/nodejs/node/pull/50354/, https://github.com/nodejs/node/pull/50364/, https://github.com/nodejs/node/pull/50505/, https://github.com/nodejs/node/pull/50303/, https://github.com/nodejs/node/pull/50385/, https://github.com/nodejs/node/pull/50209/, https://github.com/nodejs/node/pull/50237/, https://github.com/nodejs/node/pull/50515/, https://github.com/nodejs/node/pull/50327/, https://github.com/nodejs/node/pull/50115/, https://github.com/nodejs/node/pull/50443/, https://github.com/nodejs/node/pull/50466/, https://github.com/nodejs/node/pull/50492/)
Appeared test-rackspace-centos7-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/55382/
Last CI https://ci.nodejs.org/job/node-test-pull-request/55458/
Example
fatal error: string_view: No such file or directory

Reason fatal: No rebase in progress?
Type BUILD_FAILURE
Failed PR 12 (https://github.com/nodejs/node/pull/50492/, https://github.com/nodejs/node/pull/50443/, https://github.com/nodejs/node/pull/50488/, https://github.com/nodejs/node/pull/50505/, https://github.com/nodejs/node/pull/50506/, https://github.com/nodejs/node/pull/50515/, https://github.com/nodejs/node/pull/50303/, https://github.com/nodejs/node/pull/50518/, https://github.com/nodejs/node/pull/50237/, https://github.com/nodejs/node/pull/50385/, https://github.com/nodejs/node/pull/50531/, https://github.com/nodejs/node/pull/50115/)
Appeared test-softlayer-debian10-x64-1, test-ibm-ubi81_container-x64-1, test-nearform-macos10.15-x64-3, test-osuosl-rhel8-ppc64_le-2, test-osuosl-rhel8-ppc64_le-4, test-osuosl-rhel8-ppc64_le-1, test-osuosl-rhel8-ppc64_le-3, test-ibm-rhel8-s390x-4, test-nearform-macos11.0-arm64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/55372/
Last CI https://ci.nodejs.org/job/node-test-pull-request/55447/
Example
fatal: No rebase in progress?

Reason fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository
Type BUILD_FAILURE
Failed PR 10 (https://github.com/nodejs/node/pull/50443/, https://github.com/nodejs/node/pull/50425/, https://github.com/nodejs/node/pull/50505/, https://github.com/nodejs/node/pull/50385/, https://github.com/nodejs/node/pull/50531/, https://github.com/nodejs/node/pull/48059/, https://github.com/nodejs/node/pull/50354/, https://github.com/nodejs/node/pull/50115/, https://github.com/nodejs/node/pull/50574/, https://github.com/nodejs/node/pull/50555/)
Appeared test-equinix-ubuntu2004_container-armv7l-1
First CI https://ci.nodejs.org/job/node-test-pull-request/55379/
Last CI https://ci.nodejs.org/job/node-test-pull-request/55463/
Example
fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository
fatal: Could not read from remote repository.
fatal: failed to run repack

Reason FATAL: script not yet approved for use
Type BUILD_FAILURE
Failed PR 7 (https://github.com/nodejs/node/pull/50354/, https://github.com/nodejs/node/pull/50364/, https://github.com/nodejs/node/pull/50505/, https://github.com/nodejs/node/pull/50303/, https://github.com/nodejs/node/pull/50385/, https://github.com/nodejs/node/pull/50209/, https://github.com/nodejs/node/pull/50237/)
Appeared test-equinix-ubuntu2204-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/55384/
Last CI https://ci.nodejs.org/job/node-test-pull-request/55393/
Example
FATAL: script not yet approved for use
org.jenkinsci.plugins.scriptsecurity.scripts.UnapprovedUsageException: script not yet approved for use
	at org.jenkinsci.plugins.scriptsecurity.scripts.ScriptApproval.using(ScriptApproval.java:645)
	at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SecureGroovyScript.evaluate(SecureGroovyScript.java:373)
	at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SecureGroovyScript.evaluate(SecureGroovyScript.java:310)
	at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SecureGroovyScript$evaluate.call(Unknown Source)

Reason ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
Type BUILD_FAILURE
Failed PR 4 (https://github.com/nodejs/node/pull/50515/, https://github.com/nodejs/node/pull/50493/, https://github.com/nodejs/node/pull/50115/, https://github.com/nodejs/node/pull/50555/)
Appeared test-equinix-ubuntu2004_container-armv7l-1, test-osuosl-ubuntu2004_container-armv7l-1, test-equinix-centos7_container-arm64-1, test-equinix-centos7_container-arm64-2, test-equinix-rhel8_container-arm64-1, test-equinix-ubuntu1804_sharedlibs_container-arm64-1, test-osuosl-aix72-ppc64_be-3, test-ibm-aix72-ppc64_be-2
First CI https://ci.nodejs.org/job/node-test-pull-request/55398/
Last CI https://ci.nodejs.org/job/node-test-pull-request/55460/
Example
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
[PostBuildScript] - [INFO] Executing post build scripts.
[node-test-binary-armv7l] $ /bin/bash -ex /tmp/jenkins1573036626064443349.sh
+ '[' -d .git ']'
+ git clean -fdx

Reason error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj]
Type BUILD_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/50552/, https://github.com/nodejs/node/pull/50115/, https://github.com/nodejs/node/pull/50558/)
Appeared test-rackspace-win2022_vs2022-x64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/55443/
Last CI https://ci.nodejs.org/job/node-test-pull-request/55449/
Example
error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj]
  property-cell-tq-csa.cc
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.36.32532\include\tuple(622): fatal  error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj]
  scope-info-tq-csa.cc
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.36.32532\include\tuple(625): fatal  error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj]

Reason fatal error: charconv: No such file or directory
Type BUILD_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/50385/, https://github.com/nodejs/node/pull/50515/)
Appeared test-equinix_mnx-smartos18-x64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/55385/
Last CI https://ci.nodejs.org/job/node-test-pull-request/55398/
Example
fatal error: charconv: No such file or directory

Reason fatal error: ld terminated with signal 11 [Segmentation fault], core dumped
Type BUILD_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/50303/, https://github.com/nodejs/node/pull/50425/)
Appeared test-osuosl-rhel8-ppc64_le-4
First CI https://ci.nodejs.org/job/node-test-pull-request/55390/
Last CI https://ci.nodejs.org/job/node-test-pull-request/55396/
Example
fatal error: ld terminated with signal 11 [Segmentation fault], core dumped

JSTest Failure
Reason parallel/test-tls-ticket-cluster
Type JS_TEST_FAILURE
Failed PR 4 (https://github.com/nodejs/node/pull/50303/, https://github.com/nodejs/node/pull/50237/, https://github.com/nodejs/node/pull/50506/, https://github.com/nodejs/node/pull/50574/)
Appeared test-rackspace-win2016_vs2015-x64-1, test-rackspace-win2016_vs2015-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/55405/
Last CI https://ci.nodejs.org/job/node-test-pull-request/55462/
Example
not ok 750 parallel/test-tls-ticket-cluster
  ---
  duration_ms: 1064.98800
  severity: fail
  exitcode: 3221226505
  stack: |-
    [primary] got "listening"
    [primary] connecting 49769 session? false
    [primary] got "listening"
    [primary] got "listening"
    [primary] got "listening"
    [worker] connection reused? false
    [primary] got "not-reused"
    [primary] connecting 49769 session? true
    [worker] connection reused? true
    [primary] got "reused"
    [primary] connecting 49769 session? true
    [worker] connection reused? true
    [primary] got "reused"
    [primary] connecting 49769 session? true
    [worker] connection reused? true
    [primary] got "reused"
    [primary] connecting 49769 session? true
    [worker] connection reused? true
    [primary] got "reused"
    [primary] connecting 49769 session? true
    [worker] connection reused? true
    [primary] got "reused"
    [primary] connecting 49769 session? true
    [worker] connection reused? true
    [primary] got "reused"
    [pr...

Reason parallel/test-fs-write-stream-eagain
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/50237/, https://github.com/nodejs/node/pull/50492/)
Appeared test-digitalocean-fedora38-x64-2, test-ibm-aix72-ppc64_be-2
First CI https://ci.nodejs.org/job/node-test-pull-request/55393/
Last CI https://ci.nodejs.org/job/node-test-pull-request/55440/
Example
not ok 1243 parallel/test-fs-write-stream-eagain
  ---
  duration_ms: 214.95900
  severity: fail
  exitcode: 1
  stack: |-
    TAP version 13
    # Subtest: WriteStream EAGAIN
        # Subtest: _write
        not ok 1 - _write
          ---
          duration_ms: 12.876524
          location: 'file:///home/iojs/build/workspace/node-test-commit-linux/test/parallel/test-fs-write-stream-eagain.mjs:15:3'
          failureType: 'testCodeFailure'
          error: |-
            Expected values to be strictly equal:
            
            '' !== 'foo'
            
          code: 'ERR_ASSERTION'
          name: 'AssertionError'
          expected: 'foo'
          actual: ''
          operator: 'strictEqual'
          stack: |-
            TestContext.<anonymous> (file:///home/iojs/build/workspace/node-test-commit-linux/test/parallel/test-fs-write-stream-eagain.mjs:30:12)
            process.processTicksAndRejections (node:internal/process/task_queues:95:5)
            async Test.run (node:internal/test_runner/tes...

Reason parallel/test-navigator
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/50385/, https://github.com/nodejs/node/pull/50303/)
Appeared test-azure_msft-win2016_vs2017-x64-5, test-rackspace-win2019_vs2019-x64-3, test-rackspace-win2022_vs2022-x64-3, test-azure_msft-win11_vs2022-arm64-1, test-azure_msft-win11_vs2022-arm64-5, test-azure_msft-win2016_vs2017-x64-1, test-rackspace-win2019_vs2019-x64-4, test-azure_msft-win2022_vs2019-x64-2, test-azure_msft-win11_vs2022-arm64-4, test-rackspace-win2019_vs2019-x64-1, test-rackspace-win2022_vs2022-x64-6, test-azure_msft-win11_vs2022-arm64-3, test-osuosl-aix72-ppc64_be-3, test-ibm-aix72-ppc64_be-2
First CI https://ci.nodejs.org/job/node-test-pull-request/55371/
Last CI https://ci.nodejs.org/job/node-test-pull-request/55405/
Example
not ok 526 parallel/test-navigator
  ---
  duration_ms: 328.01300
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:991
        throw newErr;
        ^
    
    AssertionError [ERR_ASSERTION]: ifError got unwanted exception: Command failed: C:\workspace\node-test-binary-windows-js-suites\node\Release\node.exe -p process.exit(navigator.language === "fr-FR" ? 0 : 1)
    
        at C:\workspace\node-test-binary-windows-js-suites\node\test\common\index.js:439:12
        at C:\workspace\node-test-binary-windows-js-suites\node\test\common\index.js:476:15
        at ChildProcess.exithandler (node:child_process:430:5)
        at ChildProcess.exithandler (node:child_process:422:12)
        at ChildProcess.emit (node:events:519:28)
        at maybeClose (node:internal/child_process:1105:16)
        at Socket.<anonymous> (node:internal/child_process:457:11)
        at Socket.emit (node:events:519:28)
        at Pipe.<anonymous> (node:net:337:12) {
      generatedMessage: false,
      code: 'ERR_ASSERTION',
   ...

Reason parallel/test-string-decoder
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/50506/, https://github.com/nodejs/node/pull/50558/)
Appeared test-rackspace-win2016_vs2015-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/55425/
Last CI https://ci.nodejs.org/job/node-test-pull-request/55451/
Example
not ok 717 parallel/test-string-decoder
  ---
  duration_ms: 315.99900
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:635
          throw err;
          ^
    
    AssertionError [ERR_ASSERTION]: Expected values to be strictly deep-equal:
    + actual - expected
    
    + Comparison {}
    - Comparison {
    -   code: 'ERR_STRING_TOO_LONG'
    - }
        at Object.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-string-decoder.js:205:10)
        at Module._compile (node:internal/modules/cjs/loader:1241:14)
        at Module._extensions..js (node:internal/modules/cjs/loader:1295:10)
        at Module.load (node:internal/modules/cjs/loader:1091:32)
        at Module._load (node:internal/modules/cjs/loader:938:12)
        at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:83:12)
        at node:internal/main/run_main_module:23:47 {
      generatedMessage: true,
      code: 'ERR_ASSERTION',
      actual: RangeError: Array buffer allocat...

Reason parallel/test-worker-http2-stream-terminate
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/50558/, https://github.com/nodejs/node/pull/50574/)
Appeared test-rackspace-win2019_vs2019-x64-3, test-azure_msft-win2016_vs2017-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/55451/
Last CI https://ci.nodejs.org/job/node-test-pull-request/55462/
Example
not ok 858 parallel/test-worker-http2-stream-terminate
  ---
  duration_ms: 598.99500
  severity: crashed
  exitcode: 3221225477
  stack: |-
  ...


Progress
  • Backing channel 'JNLP4-connect connection from ... is disconnected. (3)
  • Build timed out (after 120 minutes). Marking the build as failed. (2)
  • ERROR: Error fetching remote repo 'origin' (6)
  • fatal error: string_view: No such file or directory (14)
  • fatal: No rebase in progress? (12)
  • fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository (10)
  • FATAL: script not yet approved for use (7)
  • ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (4)
  • error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj] (3)
  • fatal error: charconv: No such file or directory (2)
  • fatal error: ld terminated with signal 11 [Segmentation fault], core dumped (2)
  • parallel/test-tls-ticket-cluster (4)
  • parallel/test-fs-write-stream-eagain (2)
  • parallel/test-navigator (2)
  • parallel/test-string-decoder (2)
  • parallel/test-worker-http2-stream-terminate (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.