nodejs / nodejs/reliability

CI Reliability 2022-08-10

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

Nobody has claimed this yet.

Dominant language
Shell
Stars
57
Forks
20
PR merge metrics
No merged PRs in 30d

Description

Failures in node-test-pull-request/45859 to node-test-pull-request/45958 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-10 00:14 0 5 32 4 59 5.21%
Jenkins Failure
Reason Backing channel 'JNLP4-connect connection from ... is disconnected.
Type JENKINS_FAILURE
Failed PR 4 (https://github.com/nodejs/node/pull/44100/, https://github.com/nodejs/node/pull/44016/, https://github.com/nodejs/node/pull/44157/, https://github.com/nodejs/node/pull/44141/)
Appeared test-digitalocean-freebsd12-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/45875/
Last CI https://ci.nodejs.org/job/node-test-pull-request/45940/
Example
java.io.IOException: Backing channel 'JNLP4-connect connection from 107.170.28.213/107.170.28.213:35716' 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

undefined
Reason Unknown
Type undefined
Failed PR 13 (https://github.com/nodejs/node/pull/44140/, https://github.com/nodejs/node/pull/44163/, https://github.com/nodejs/node/pull/44155/, https://github.com/nodejs/node/pull/44157/, https://github.com/nodejs/node/pull/44149/, 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/44095/, https://github.com/nodejs/node/pull/44074/)
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/45861/
Last CI https://ci.nodejs.org/job/node-test-pull-request/45958/
Example
Unknown

JSTest Failure
Reason parallel/test-diagnostics-channel-net
Type JS_TEST_FAILURE
Failed PR 8 (https://github.com/nodejs/node/pull/44140/, https://github.com/nodejs/node/pull/43455/, https://github.com/nodejs/node/pull/44146/, https://github.com/nodejs/node/pull/44139/, https://github.com/nodejs/node/pull/44100/, https://github.com/nodejs/node/pull/44155/, https://github.com/nodejs/node/pull/44141/, https://github.com/nodejs/node/pull/44016/)
Appeared undefined
First CI https://ci.nodejs.org/job/node-test-pull-request/45861/
Last CI https://ci.nodejs.org/job/node-test-pull-request/45891/
Example
not ok 653 parallel/test-diagnostics-channel-net
  ---
  duration_ms: 0.335
  severity: fail
  exitcode: 1
  stack: |-
    Mismatched <anonymous> function calls. Expected exactly 1, actual 0.
  ...


Reason node-api/test_threadsafe_function/test
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/44149/, https://github.com/nodejs/node/pull/43700/)
Appeared test-equinix-ubuntu2004_container-armv7l-1
First CI https://ci.nodejs.org/job/node-test-pull-request/45907/
Last CI https://ci.nodejs.org/job/node-test-pull-request/45947/
Example
not ok 104 node-api/test_threadsafe_function/test
  ---
  duration_ms: 360.27
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason parallel/test-debugger-extract-function-name
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/44140/, https://github.com/nodejs/node/pull/43521/)
Appeared test-azure_msft-win10_vs2019-x64-4, test-azure_msft-win10_vs2019-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/45861/
Last CI https://ci.nodejs.org/job/node-test-pull-request/45923/
Example
not ok 215 parallel/test-debugger-extract-function-name
  ---
  duration_ms: 6.609
  severity: fail
  exitcode: 1
  stack: |-
    C:\workspace\node-test-binary-windows-js-suites\node\test\common\debugger.js:84
              reject(new Error([
                     ^
    
    Error: Timeout (5000) while waiting for /break (?:on start )?in/i; found: connecting to 127.0.0.1:9229 ...
    < Debugger listening on ws://127.0.0.1:9229/10a42809-38d1-4225-a6fa-ecd6b90a79fe
    < 
    
    < For help, see: https://nodejs.org/en/docs/inspector
    < 
    
     ok
    < Debugger attached.
    < 
    
    debug> 
        at Timeout.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\common\debugger.js:84:18)
        at listOnTimeout (node:internal/timers:564:17)
        at process.processTimers (node:internal/timers:507:7)
    
    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)
       ...

Progress
  • Backing channel 'JNLP4-connect connection from ... is disconnected. (4)
  • ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (3)
  • Unknown (13)
  • parallel/test-diagnostics-channel-net (8)
  • node-api/test_threadsafe_function/test (2)
  • parallel/test-debugger-extract-function-name (2)
  • parallel/test-vm-timeout-escape-promise-2 (2)

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.

Research direction

Start with the Jenkins console links and the generated failure report, then compare the listed failures across their first and last CI runs. The issue names several infrastructure and test failures but does not specify a target file, entry point, or single completion criterion; a useful outcome would need to identify which failure is in scope and how it should be verified.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
ci-cd, devops, testing-qa
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.