CI Reliability 2022-12-20

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

Research direction

Start with the generated reliability report in reliability/results.md and the ncu-ci walk pr --stats=true command shown in the issue. Review the linked Jenkins jobs and grouped failures, but the issue does not define a specific component to change or a clear completion condition.

Written by the indexing model from the issue text.

Description

Failures in node-test-pull-request/48518 to node-test-pull-request/48613 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-20 00:13 7 3 8 22 60 4.23%
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/45870/, https://github.com/nodejs/node/pull/45869/, https://github.com/nodejs/node/pull/45902/)
Appeared test-nearform_arm-win10_vs2019-arm64-2, test-nearform_arm-win10_vs2019-arm64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/48518/
Last CI https://ci.nodejs.org/job/node-test-pull-request/48560/
Example
java.io.IOException: Backing channel 'JNLP4-connect connection from ip-83-147-191-74.broadband.digiweb.ie/83.147.191.74:49828' 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)

Reason Build timed out (after 60 minutes). Marking the build as failed.
Type JENKINS_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/45869/, https://github.com/nodejs/node/pull/45857/, https://github.com/nodejs/node/pull/45486/)
Appeared test-softlayer-ubi81_container-x64-1, test-rackspace-win2012r2_vs2019-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/48530/
Last CI https://ci.nodejs.org/job/node-test-pull-request/48574/
Example
Build timed out (after 60 minutes). Marking the build as failed.

Git Failure
Reason ERROR: Error fetching remote repo 'origin'
Type GIT_FAILURE
Failed PR 14 (https://github.com/nodejs/node/pull/45608/, https://github.com/nodejs/node/pull/44445/, https://github.com/nodejs/node/pull/45894/, https://github.com/nodejs/node/pull/45712/, https://github.com/nodejs/node/pull/45877/, https://github.com/nodejs/node/pull/45885/, https://github.com/nodejs/node/pull/45882/, https://github.com/nodejs/node/pull/45887/, https://github.com/nodejs/node/pull/45258/, https://github.com/nodejs/node/pull/45793/, https://github.com/nodejs/node/pull/45547/, https://github.com/nodejs/node/pull/45857/, https://github.com/nodejs/node/pull/45895/, https://github.com/nodejs/node/pull/45886/)
Appeared test-nearform-macos10.15-x64-3, test-orka-macos10.15-x64-2, test-orka-macos11-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/48519/
Last CI https://ci.nodejs.org/job/node-test-pull-request/48613/
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:1003)
	at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1244)
	at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1308)
	at hudson.scm.SCM.checkout(SCM.java:540)

Build Failure
Reason ERROR: No acceptable C compiler found!
Type BUILD_FAILURE
Failed PR 11 (https://github.com/nodejs/node/pull/45712/, https://github.com/nodejs/node/pull/45877/, https://github.com/nodejs/node/pull/45885/, https://github.com/nodejs/node/pull/45882/, https://github.com/nodejs/node/pull/45887/, https://github.com/nodejs/node/pull/45258/, https://github.com/nodejs/node/pull/45793/, https://github.com/nodejs/node/pull/45547/, https://github.com/nodejs/node/pull/45857/, https://github.com/nodejs/node/pull/45895/, https://github.com/nodejs/node/pull/45886/)
Appeared test-orka-macos10.14-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/48583/
Last CI https://ci.nodejs.org/job/node-test-pull-request/48613/
Example
ERROR: No acceptable C compiler found!

       Please make sure you have a C compiler installed on your system and/or
       consider adjusting the CC environment variable if you installed
       it in a non-standard prefix.
make: *** [build-ci] Error 1

Reason ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error?
Type BUILD_FAILURE
Failed PR 7 (https://github.com/nodejs/node/pull/45857/, https://github.com/nodejs/node/pull/45712/, https://github.com/nodejs/node/pull/45895/, https://github.com/nodejs/node/pull/45869/, https://github.com/nodejs/node/pull/45803/, https://github.com/nodejs/node/pull/45793/, https://github.com/nodejs/node/pull/45547/)
Appeared test-nearform_arm-win10_vs2019-arm64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/48555/
Last CI https://ci.nodejs.org/job/node-test-pull-request/48603/
Example
ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error?
Collecting metadata...
Metadata collection done.
Notifying upstream projects of job completion
Finished: FAILURE

Reason Error: getWindowSize EINVAL
Type BUILD_FAILURE
Failed PR 6 (https://github.com/nodejs/node/pull/45803/, https://github.com/nodejs/node/pull/45608/, https://github.com/nodejs/node/pull/45877/, https://github.com/nodejs/node/pull/45894/, https://github.com/nodejs/node/pull/45258/, https://github.com/nodejs/node/pull/45887/)
Appeared test-equinix_mnx-smartos18-x64-4, test-equinix_mnx-smartos20-x64-4, test-equinix_mnx-smartos18-x64-3, test-equinix_mnx-smartos20-x64-3, test-joyent-smartos18-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/48528/
Last CI https://ci.nodejs.org/job/node-test-pull-request/48598/
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)

Reason ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ...
Type BUILD_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/45870/, https://github.com/nodejs/node/pull/45608/)
Appeared test-nearform-macos11.0-arm64-1, test-nearform-macos10.15-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/48518/
Last CI https://ci.nodejs.org/job/node-test-pull-request/48519/
Example
ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for node-test-commit-osx-arm/nodes=osx11 #9023
Collecting metadata...
Metadata collection done.
Notifying upstream projects of job completion
Finished: FAILURE

Reason Failed to trigger sub builds
Type BUILD_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/45865/, https://github.com/nodejs/node/pull/45401/)
Appeared undefined
First CI https://ci.nodejs.org/job/node-test-pull-request/48532/
Last CI https://ci.nodejs.org/job/node-test-pull-request/48604/
Example
Failed to trigger sub builds

JSTest Failure
Reason parallel/test-fs-watch-recursive
Type JS_TEST_FAILURE
Failed PR 7 (https://github.com/nodejs/node/pull/45886/, https://github.com/nodejs/node/pull/43772/, https://github.com/nodejs/node/pull/44445/, https://github.com/nodejs/node/pull/45895/, https://github.com/nodejs/node/pull/45712/, https://github.com/nodejs/node/pull/45857/, https://github.com/nodejs/node/pull/45882/)
Appeared test-nearform-macos11.0-arm64-1, test-orka-macos11-x64-1, test-orka-macos10.15-x64-2, test-orka-macos11-x64-2, test-softlayer-alpine311_container-x64-1, test-digitalocean-ubuntu1804_sharedlibs_container-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/48523/
Last CI https://ci.nodejs.org/job/node-test-pull-request/48597/
Example
not ok 3643 parallel/test-fs-watch-recursive
  ---
  duration_ms: 360.72
  severity: fail
  exitcode: -15
  stack: |-
    timeout
    (node:50205) 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-cwd
Type JS_TEST_FAILURE
Failed PR 5 (https://github.com/nodejs/node/pull/45803/, https://github.com/nodejs/node/pull/45902/, https://github.com/nodejs/node/pull/45865/, https://github.com/nodejs/node/pull/45851/, https://github.com/nodejs/node/pull/45869/)
Appeared test-nearform_arm-win10_vs2019-arm64-2, test-nearform_arm-win10_vs2019-arm64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/48550/
Last CI https://ci.nodejs.org/job/node-test-pull-request/48607/
Example
not ok 102 parallel/test-child-process-cwd
  ---
  duration_ms: 0.445
  severity: fail
  exitcode: 1
  stack: |-
    Can't clean tmpdir: c:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.103
    Files blocking: []
    
    node:assert:124
      throw new AssertionError(obj);
      ^
    
    AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
    + actual - expected
    
    + 'C:\\Windows'
    - 'C:\\WINDOWS'
            ^
        at ChildProcess.<anonymous> (c:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-child-process-cwd.js:56:26)
        at ChildProcess.<anonymous> (c:\workspace\node-test-binary-windows-js-suites\node\test\common\index.js:448:15)
        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: 'C:\\Windows',
      expected: 'C:\\WINDOWS',
   ...

Reason parallel/test-child-process-exec-cwd
Type JS_TEST_FAILURE
Failed PR 5 (https://github.com/nodejs/node/pull/45803/, https://github.com/nodejs/node/pull/45902/, https://github.com/nodejs/node/pull/45865/, https://github.com/nodejs/node/pull/45851/, https://github.com/nodejs/node/pull/45869/)
Appeared test-nearform_arm-win10_vs2019-arm64-2, test-nearform_arm-win10_vs2019-arm64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/48550/
Last CI https://ci.nodejs.org/job/node-test-pull-request/48607/
Example
not ok 104 parallel/test-child-process-exec-cwd
  ---
  duration_ms: 0.440
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:400
        throw err;
        ^
    
    AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:
    
      assert(stdout.startsWith(dir))
    
        at c:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-child-process-exec-cwd.js:38:3
        at c:\workspace\node-test-binary-windows-js-suites\node\test\common\index.js:413:17
        at c:\workspace\node-test-binary-windows-js-suites\node\test\common\index.js:448:15
        at ChildProcess.exithandler (node:child_process:411:7)
        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: false,
      expected: true,
      operator: '=='
    }
    
    Node.js v20.0.0-pre
  ...


Reason pummel/test-net-throttle
Type JS_TEST_FAILURE
Failed PR 4 (https://github.com/nodejs/node/pull/45886/, https://github.com/nodejs/node/pull/45885/, https://github.com/nodejs/node/pull/45857/, https://github.com/nodejs/node/pull/45258/)
Appeared test-digitalocean-freebsd12-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/48523/
Last CI https://ci.nodejs.org/job/node-test-pull-request/48601/
Example
not ok 3472 pummel/test-net-throttle
  ---
  duration_ms: 0.555
  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 parallel/test-watch-mode-files_watcher
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/45857/, https://github.com/nodejs/node/pull/45793/)
Appeared test-orka-macos11-x64-2, test-softlayer-ubuntu1804_sharedlibs_container-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/48534/
Last CI https://ci.nodejs.org/job/node-test-pull-request/48602/
Example
not ok 3441 parallel/test-watch-mode-files_watcher
  ---
  duration_ms: 120.80
  severity: fail
  exitcode: -15
  stack: |-
    timeout
    TAP version 13
    # Subtest: watch mode file watcher
        # Subtest: should watch changed files
        ok 1 - should watch changed files
          ---
          duration_ms: 19.448428
          ...


Reason wpt/test-timers
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/45877/, https://github.com/nodejs/node/pull/45847/)
Appeared test-ibm-rhel8-s390x-4, test-digitalocean-ubuntu1804_sharedlibs_container-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/48542/
Last CI https://ci.nodejs.org/job/node-test-pull-request/48580/
Example
not ok 3868 wpt/test-timers
  ---
  duration_ms: 0.886
  severity: fail
  exitcode: 1
  stack: |-
    ---- negative-settimeout.any.js ----
    [SKIPPED] unreliable in Node.js; Refs: https://github.com/nodejs/node/issues/37672
    ---- cleartimeout-clearinterval.any.js ----
    [PASS] Clear timeout with clearInterval
    ---- cleartimeout-clearinterval.any.js ----
    [PASS] Clear interval with clearTimeout
    ---- missing-timeout-setinterval.any.js ----
    [PASS] Calling setInterval with no interval should be the same as if called with 0 interval
    ---- missing-timeout-setinterval.any.js ----
    [PASS] Calling setInterval with undefined interval should be the same as if called with 0 interval
    ---- negative-setinterval.any.js ----
    [PASS] Untitled
    [UNEXPECTED_FAILURE][UNCAUGHT] evaluation in WPTRunner.runJsTests()
    assert_unreached: Reached unreachable code
    {
      message: 'assert_unreached: Reached unreachable code',
      stack: '    at listOnTimeout (node:internal/timers:564:17)\n' +...

Progress
  • Backing channel 'JNLP4-connect connection from ... is disconnected. (3)
  • Build timed out (after 60 minutes). Marking the build as failed. (3)
  • ERROR: Error fetching remote repo 'origin' (14)
  • ERROR: No acceptable C compiler found! (11)
  • ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error? (7)
  • Error: getWindowSize EINVAL (6)
  • ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ... (2)
  • Failed to trigger sub builds (2)
  • parallel/test-fs-watch-recursive (7)
  • parallel/test-child-process-cwd (5)
  • parallel/test-child-process-exec-cwd (5)
  • pummel/test-net-throttle (4)
  • parallel/test-watch-mode-files_watcher (2)
  • wpt/test-timers (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.