nodejs / nodejs/reliability

CI Reliability 2022-08-16

Open
#348 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/45939 to node-test-pull-request/46038 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-16 00:18 0 8 42 3 47 8.25%
JSTest Failure
Reason node-api/test_threadsafe_function/test
Type JS_TEST_FAILURE
Failed PR 4 (https://github.com/nodejs/node/pull/43700/, https://github.com/nodejs/node/pull/44201/, https://github.com/nodejs/node/pull/44204/, https://github.com/nodejs/node/pull/44229/)
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/46022/
Example
not ok 104 node-api/test_threadsafe_function/test
  ---
  duration_ms: 360.39
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason parallel/test-vm-timeout-escape-promise-2
Type JS_TEST_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/44217/, https://github.com/nodejs/node/pull/44216/, https://github.com/nodejs/node/pull/44220/)
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/46009/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46030/
Example
not ok 750 parallel/test-vm-timeout-escape-promise-2
  ---
  duration_ms: 0.363
  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)
       ...

Reason parallel/test-heapsnapshot-near-heap-limit-worker
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/44074/, https://github.com/nodejs/node/pull/44217/)
Appeared test-equinix-ubuntu2004_container-armv7l-1, test-rackspace-win2012r2_vs2019-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/45958/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46008/
Example
not ok 988 parallel/test-heapsnapshot-near-heap-limit-worker
  ---
  duration_ms: 2.628
  severity: fail
  exitcode: 1
  stack: |-
    
    Invoked NearHeapLimitCallback, processing=false, current_limit=52428800, initial_limit=52428800
    max_young_gen_size=25165824, young_gen_size=0, old_gen_size=51630820, total_size=51630820
    Estimated available memory=4200648704, estimated overhead=25165824
    Start generating Heap.20220812.005156.2504899.1.001.heapsnapshot...
    Wrote snapshot to /home/iojs/tmp/.tmp.900/Heap.20220812.005156.2504899.1.001.heapsnapshot
    
    <--- Last few GCs --->
    
    [2504899:0xf4a00708]     1501 ms: Mark-sweep (reduce) 49.1 (52.8) -> 49.1 (52.8) MB, 5.6 / 0.0 ms  (average mu = 0.142, current mu = -0.547) heap profiler; GC in old space requested
    
    
    <--- JS stacktrace --->
    
    FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
    
    node:assert:400
        throw err;
        ^
    
    AssertionError [ERR...

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 pummel/test-fs-largefile
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/43455/, https://github.com/nodejs/node/pull/44217/)
Appeared test-rackspace-win2012r2_vs2019-x64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/45950/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46009/
Example
not ok 832 pummel/test-fs-largefile
  ---
  duration_ms: 0.941
  severity: fail
  exitcode: 1
  stack: |-
    Can't clean tmpdir: C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.832
    Files blocking: [ 'large.txt' ]
    
    node:internal/fs/utils:348
        throw err;
        ^
    
    Error: ENOSPC: no space left on device, ftruncate
        at Object.ftruncateSync (node:fs:1136:3)
        at Object.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\pummel\test-fs-largefile.js:37:4)
        at Module._compile (node:internal/modules/cjs/loader:1119:14)
        at Module._extensions..js (node:internal/modules/cjs/loader:1173:10)
        at Module.load (node:internal/modules/cjs/loader:997:32)
        at Module._load (node:internal/modules/cjs/loader:838:12)
        at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:86:12)
        at node:internal/main/run_main_module:23:47 {
      errno: -4055,
      syscall: 'ftruncate',
      code: 'ENOSPC'
...

Jenkins Failure
Reason Backing channel 'JNLP4-connect connection from ... is disconnected.
Type JENKINS_FAILURE
Failed PR 5 (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/, https://github.com/nodejs/node/pull/44223/)
Appeared test-orka-macos11-x64-2, test-nearform-macos11.0-arm64-1, test-nearform-macos10.15-x64-1, test-digitalocean-freebsd12-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/45940/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46015/
Example
java.io.IOException: Backing channel 'JNLP4-connect connection from 199.7.167.102/199.7.167.102:39360' 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 workspace for ...
Type BUILD_FAILURE
Failed PR 4 (https://github.com/nodejs/node/pull/44169/, https://github.com/nodejs/node/pull/44201/, https://github.com/nodejs/node/pull/44223/, https://github.com/nodejs/node/pull/44229/)
Appeared test-digitalocean-freebsd12-x64-1, test-orka-macos10.15-x64-2, 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/46021/
Example
ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for node-test-commit-freebsd/nodes=freebsd12-x64 #45426
Collecting metadata...
Metadata collection done.
Notifying upstream projects of job completion
Finished: 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/44074/, https://github.com/nodejs/node/pull/44174/, https://github.com/nodejs/node/pull/44156/)
Appeared test-joyent-smartos20-x64-3, test-osuosl-aix72-ppc64_be-3, test-equinix-debian10_container-armv7l-2, test-equinix-ubuntu2004_container-armv7l-1, test-equinix-debian10_container-armv7l-1
First CI https://ci.nodejs.org/job/node-test-pull-request/45939/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46038/
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

undefined
Reason Unknown
Type undefined
Failed PR 12 (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/44217/, https://github.com/nodejs/node/pull/44216/, https://github.com/nodejs/node/pull/44098/, https://github.com/nodejs/node/pull/44229/, https://github.com/nodejs/node/pull/44220/)
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/45944/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46030/
Example
Unknown

Progress
  • node-api/test_threadsafe_function/test (4)
  • parallel/test-vm-timeout-escape-promise-2 (3)
  • parallel/test-heapsnapshot-near-heap-limit-worker (2)
  • parallel/test-http2-server-shutdown-options-errors (2)
  • pummel/test-fs-largefile (2)
  • Backing channel 'JNLP4-connect connection from ... is disconnected. (5)
  • ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ... (4)
  • ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (3)
  • Unknown (12)

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 generated ncu-ci walk pr --stats=true --markdown ... report and inspect the listed Node.js test, Jenkins, Git, and build failures, including the named test paths. Done would require identifying a concrete reliability change for these failures, but the issue does not specify which failure to fix or how success should be verified.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, nodejs, shell
Domain
ci-cd, devops, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.