CI Reliability 2022-08-12

Open
#344 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
javascript, node.js, shell

Research direction

Start with the linked CI and Jenkins console logs, then reproduce the named tests: node-api/test_threadsafe_function/test, parallel/test-http2-server-shutdown-options-errors, and parallel/test-vm-timeout-escape-promise-2. The report also lists JUnit publication, workspace, and unknown failures; done would require determining and resolving the causes behind the listed failures and updating the progress checklist.

Written by the indexing model from the issue text.

Description

Failures in node-test-pull-request/45908 to node-test-pull-request/46006 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-08-12 00:14 0 5 38 5 52 5.26%
JSTest Failure
Reason node-api/test_threadsafe_function/test
Type JS_TEST_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/43700/, https://github.com/nodejs/node/pull/44201/, https://github.com/nodejs/node/pull/44204/)
Appeared test-equinix-ubuntu2004_container-armv7l-1
First CI https://ci.nodejs.org/job/node-test-pull-request/45947/
Last CI https://ci.nodejs.org/job/node-test-pull-request/45983/
Example
not ok 104 node-api/test_threadsafe_function/test
  ---
  duration_ms: 360.75
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason parallel/test-http2-server-shutdown-options-errors
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/44074/, https://github.com/nodejs/node/pull/44170/)
Appeared test-rackspace-win2012r2_vs2019-x64-4, test-rackspace-win2012r2_vs2019-x64-5
First CI https://ci.nodejs.org/job/node-test-pull-request/45958/
Last CI https://ci.nodejs.org/job/node-test-pull-request/45977/
Example
not ok 428 parallel/test-http2-server-shutdown-options-errors
  ---
  duration_ms: 0.315
  severity: fail
  exitcode: 1
  stack: |-
    node:events:491
          throw er; // Unhandled 'error' event
          ^
    
    Error: read ECONNRESET
        at TCP.onStreamRead (node:internal/stream_base_commons:217:20)
    Emitted 'error' event on ClientHttp2Stream instance at:
        at emitErrorNT (node:internal/streams/destroy:151:8)
        at emitErrorCloseNT (node:internal/streams/destroy:116:3)
        at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
      errno: -4077,
      code: 'ECONNRESET',
      syscall: 'read'
    }
    
    Node.js v19.0.0-pre
  ...


Reason parallel/test-vm-timeout-escape-promise-2
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/44114/, https://github.com/nodejs/node/pull/44174/)
Appeared test-azure_msft-win10_vs2019-x64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/45915/
Last CI https://ci.nodejs.org/job/node-test-pull-request/45927/
Example
not ok 749 parallel/test-vm-timeout-escape-promise-2
  ---
  duration_ms: 0.343
  severity: fail
  exitcode: 1
  stack: |-
    C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-vm-timeout-escape-promise-2.js:20
          throw new Error(
                ^
    
    Error: escaped timeout at 100 milliseconds!
        at loop (C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-vm-timeout-escape-promise-2.js:20:13)
        at evalmachine.<anonymous>:1:30
        at Script.runInContext (node:vm:141:12)
        at Script.runInNewContext (node:vm:146:17)
        at Object.runInNewContext (node:vm:306:38)
        at assert.throws.code (C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-vm-timeout-escape-promise-2.js:27:6)
        at getActual (node:assert:757:5)
        at Function.throws (node:assert:903:24)
        at Object.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-vm-timeout-escape-promise-2.js:26:8)
       ...

Jenkins Failure
Reason Backing channel 'JNLP4-connect connection from ... is disconnected.
Type JENKINS_FAILURE
Failed PR 5 (https://github.com/nodejs/node/pull/44157/, https://github.com/nodejs/node/pull/44141/, https://github.com/nodejs/node/pull/44184/, https://github.com/nodejs/node/pull/44095/, https://github.com/nodejs/node/pull/44204/)
Appeared test-nearform-macos10.15-x64-1, test-nearform-macos11.0-arm64-1, test-digitalocean-freebsd12-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/45913/
Last CI https://ci.nodejs.org/job/node-test-pull-request/45983/
Example
java.io.IOException: Backing channel 'JNLP4-connect connection from ip-83-147-191-70.broadband.digiweb.ie/83.147.191.70:63644' is disconnected.
	at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:216)
	at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:286)
	at com.sun.proxy.$Proxy79.isAlive(Unknown Source)
	at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1213)
	at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1205)

Git Failure
Build Failure
Reason ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
Type BUILD_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/44132/, https://github.com/nodejs/node/pull/44074/, https://github.com/nodejs/node/pull/44174/)
Appeared test-equinix-debian10_container-armv7l-2, test-equinix-ubuntu2004_container-armv7l-1, test-equinix-debian10_container-armv7l-1, test-joyent-smartos20-x64-4, test-equinix-rhel8_container-arm64-2, test-equinix-ubuntu1804_container-arm64-2, test-equinix-ubuntu2004_sharedlibs_container-arm64-6, test-equinix-ubuntu1804_sharedlibs_container-arm64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/45918/
Last CI https://ci.nodejs.org/job/node-test-pull-request/45944/
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/jenkins4491082771603267883.sh
+ '[' -d .git ']'
+ git clean -fdx

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

undefined
Reason Unknown
Type undefined
Failed PR 11 (https://github.com/nodejs/node/pull/44114/, https://github.com/nodejs/node/pull/43521/, https://github.com/nodejs/node/pull/44169/, https://github.com/nodejs/node/pull/44174/, https://github.com/nodejs/node/pull/43700/, https://github.com/nodejs/node/pull/43455/, https://github.com/nodejs/node/pull/44170/, https://github.com/nodejs/node/pull/44204/, https://github.com/nodejs/node/pull/44074/, https://github.com/nodejs/node/pull/44095/, https://github.com/nodejs/node/pull/44216/)
Appeared test-nearform_arm-win10_vs2019-arm64-1, test-equinix-debian10_container-armv7l-1
First CI https://ci.nodejs.org/job/node-test-pull-request/45915/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46006/
Example
Unknown

Progress
  • node-api/test_threadsafe_function/test (3)
  • parallel/test-http2-server-shutdown-options-errors (2)
  • parallel/test-vm-timeout-escape-promise-2 (2)
  • Backing channel 'JNLP4-connect connection from ... is disconnected. (5)
  • ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (3)
  • ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ... (2)
  • Unknown (11)
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.