nodejs / nodejs/reliability

CI Reliability 2024-03-12

Open
#809 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/57602 to node-test-pull-request/57697 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
2024-03-12 00:08 1 0 25 7 67 0.00%
JSTest Failure
Reason parallel/test-domain-error-types
Type JS_TEST_FAILURE
Failed PR 18 (https://github.com/nodejs/node/pull/51998/, https://github.com/nodejs/node/pull/51999/, https://github.com/nodejs/node/pull/51996/, https://github.com/nodejs/node/pull/52000/, https://github.com/nodejs/node/pull/51880/, https://github.com/nodejs/node/pull/52005/, https://github.com/nodejs/node/pull/51992/, https://github.com/nodejs/node/pull/52010/, https://github.com/nodejs/node/pull/52016/, https://github.com/nodejs/node/pull/52028/, https://github.com/nodejs/node/pull/51866/, https://github.com/nodejs/node/pull/52009/, https://github.com/nodejs/node/pull/52036/, https://github.com/nodejs/node/pull/52040/, https://github.com/nodejs/node/pull/51791/, https://github.com/nodejs/node/pull/52024/, https://github.com/nodejs/node/pull/52039/, https://github.com/nodejs/node/pull/52037/)
Appeared test-equinix-ubuntu2004_sharedlibs_container-arm64-5, test-equinix-ubuntu2004_sharedlibs_container-arm64-6, test-equinix-ubuntu2004_sharedlibs_container-arm64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/57604/
Last CI https://ci.nodejs.org/job/node-test-pull-request/57693/
Example
not ok 949 parallel/test-domain-error-types
  ---
  duration_ms: 1531.32200
  severity: crashed
  exitcode: -11
  stack: |-
  ...


Reason parallel/test-debugger-heap-profiler
Type JS_TEST_FAILURE
Failed PR 9 (https://github.com/nodejs/node/pull/52009/, https://github.com/nodejs/node/pull/51972/, https://github.com/nodejs/node/pull/52037/, https://github.com/nodejs/node/pull/52027/, https://github.com/nodejs/node/pull/52040/, https://github.com/nodejs/node/pull/52016/, https://github.com/nodejs/node/pull/51866/, https://github.com/nodejs/node/pull/52024/, https://github.com/nodejs/node/pull/52023/)
Appeared test-azure_msft-win11_vs2022-arm64-4, test-azure_msft-win2016_vs2017-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/57665/
Last CI https://ci.nodejs.org/job/node-test-pull-request/57688/
Example
not ok 182 parallel/test-debugger-heap-profiler
  ---
  duration_ms: 2464.99000
  severity: fail
  exitcode: 1
  stack: |-
    Can't clean tmpdir: d:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.180
    Files blocking: [ 'node.heapsnapshot' ]
    
    d:\workspace\node-test-binary-windows-js-suites\node\test\common\tmpdir.js:69
        throw e;
        ^
    
    Error: EBUSY: resource busy or locked, rmdir 'd:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.180'
        at rmdirSync (node:fs:1219:11)
        at _rmdirSync (node:internal/fs/rimraf:235:5)
        at rimrafSync (node:internal/fs/rimraf:193:7)
        at Object.rmSync (node:fs:1268:10)
        at rmSync (d:\workspace\node-test-binary-windows-js-suites\node\test\common\tmpdir.js:20:8)
        at onexit (d:\workspace\node-test-binary-windows-js-suites\node\test\common\tmpdir.js:54:5)
        at process.<anonymous> (d:\workspace\node-test-binary-windows-js-suites\node\test\common\tmpdir.js:43:14)
        at process.emit (...

Reason parallel/test-child-process-exec-encoding
Type JS_TEST_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/51719/, https://github.com/nodejs/node/pull/52010/, https://github.com/nodejs/node/pull/52027/)
Appeared test-rackspace-win2019_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/57612/
Last CI https://ci.nodejs.org/job/node-test-pull-request/57674/
Example
not ok 102 parallel/test-child-process-exec-encoding
  ---
  duration_ms: 870.05200
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:1000
        throw newErr;
        ^
    
    AssertionError [ERR_ASSERTION]: ifError got unwanted exception: Command failed: "C:\workspace\node-test-binary-windows-js-suites\node\Release\node.exe" "C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-child-process-exec-encoding.js" child
    
    
    #
    
    # Fatal process out of memory: Re-embedded builtins: set permissions
    
    #
    
    
    
    
        at C:\workspace\node-test-binary-windows-js-suites\node\test\common\index.js:436:12
        at C:\workspace\node-test-binary-windows-js-suites\node\test\common\index.js:473:15
        at ChildProcess.exithandler (node:child_process:430:5)
        at genericNodeError (node:internal/errors:984:15)
        at wrappedFn (node:internal/errors:538:14)
        at ChildProcess.exithandler (node:child_process:422:12)
        at ChildProcess.emi...

Reason parallel/test-child-process-exec-maxbuf
Type JS_TEST_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/51719/, https://github.com/nodejs/node/pull/52010/, https://github.com/nodejs/node/pull/52027/)
Appeared test-rackspace-win2019_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/57612/
Last CI https://ci.nodejs.org/job/node-test-pull-request/57674/
Example
not ok 98 parallel/test-child-process-exec-maxbuf
  ---
  duration_ms: 634.02800
  severity: fail
  exitcode: 1
  stack: |-
    node:internal/child_process:421
        throw new ErrnoException(err, 'spawn');
        ^
    
    Error: spawn UNKNOWN
        at ChildProcess.spawn (node:internal/child_process:421:11)
        at spawn (node:child_process:761:9)
        at Object.execFile (node:child_process:351:17)
        at Object.exec (node:child_process:234:25)
        at Object.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-child-process-exec-maxbuf.js:116:20)
        at Module._compile (node:internal/modules/cjs/loader:1368:14)
        at Module._extensions..js (node:internal/modules/cjs/loader:1426:10)
        at Module.load (node:internal/modules/cjs/loader:1205:32)
        at Module._load (node:internal/modules/cjs/loader:1021:12)
        at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:177:12) {
      errno: -4094,
      code: 'UNKNOWN',...

Reason parallel/test-cluster-fork-stdio
Type JS_TEST_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/51977/, https://github.com/nodejs/node/pull/51996/, https://github.com/nodejs/node/pull/52002/)
Appeared test-rackspace-win2016_vs2015-x64-1, test-rackspace-win2019_vs2019-x64-4, test-azure_msft-win11_vs2022-arm64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/57603/
Last CI https://ci.nodejs.org/job/node-test-pull-request/57616/
Example
not ok 919 parallel/test-cluster-fork-stdio
  ---
  duration_ms: 120225.48000
  severity: fail
  exitcode: 1
  stack: |-
    timeout
  ...


Reason sequential/test-worker-fshandles-open-close-on-termination
Type JS_TEST_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/51719/, https://github.com/nodejs/node/pull/52002/, https://github.com/nodejs/node/pull/52023/)
Appeared test-azure_msft-win11_vs2022-x64-1, test-rackspace-win2022_vs2022-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/57612/
Last CI https://ci.nodejs.org/job/node-test-pull-request/57688/
Example
not ok 973 sequential/test-worker-fshandles-open-close-on-termination
  ---
  duration_ms: 522.00400
  severity: fail
  exitcode: 3221226356
  stack: |-
  ...


Reason benchmark/test-benchmark-http2
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/51973/, https://github.com/nodejs/node/pull/52037/)
Appeared test-azure_msft-win2016_vs2017-x64-1, test-azure_msft-win2016_vs2017-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/57602/
Last CI https://ci.nodejs.org/job/node-test-pull-request/57696/
Example
not ok 184 benchmark/test-benchmark-http2
  ---
  duration_ms: 2075.89100
  severity: fail
  exitcode: 1
  stack: |-
    Error: test-double-http2 failed with 3221226505.
        at ChildProcess.<anonymous> (C:\workspace\node-test-binary-windows-native-suites\node\benchmark\_http-benchmarkers.js:242:16)
        at Object.onceWrapper (node:events:632:26)
        at ChildProcess.emit (node:events:517:28)
        at maybeClose (node:internal/child_process:1098:16)
        at ChildProcess._handle.onexit (node:internal/child_process:303:5)
    node:assert:125
      throw new AssertionError(obj);
      ^
    
    AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
    
    3221226505 !== 0
    
        at ChildProcess.<anonymous> (C:\workspace\node-test-binary-windows-native-suites\node\test\common\benchmark.js:28:12)
        at ChildProcess.emit (node:events:517:28)
        at ChildProcess._handle.onexit (node:internal/child_process:292:12) {
      generatedMessage: true,
      code: 'ERR_ASSERTIO...

Reason benchmark/test-benchmark-net
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/51973/, https://github.com/nodejs/node/pull/52037/)
Appeared test-azure_msft-win10_vs2019-x64-2, test-azure_msft-win11_vs2022-x64-4, test-azure_msft-win11_vs2022-arm64-4, test-rackspace-win2019_vs2019-x64-3, test-rackspace-win2022_vs2022-x64-2, test-azure_msft-win11_vs2022-x64-2, test-azure_msft-win11_vs2022-arm64-2, test-rackspace-win2019_vs2019-x64-1, test-rackspace-win2022_vs2022-x64-4, test-azure_msft-win10_vs2019-x64-4, test-rackspace-win2022_vs2022-x64-5, test-rackspace-win2022_vs2022-x64-3, test-azure_msft-win10_vs2019-x64-3, test-rackspace-win2019_vs2019-x64-2, test-rackspace-win2022_vs2022-x64-6
First CI https://ci.nodejs.org/job/node-test-pull-request/57666/
Last CI https://ci.nodejs.org/job/node-test-pull-request/57696/
Example
not ok 195 benchmark/test-benchmark-net
  ---
  duration_ms: 965.43200
  severity: fail
  exitcode: 1
  stack: |-
    node:events:497
          throw er; // Unhandled 'error' event
          ^
    
    Error: write ENOBUFS
        at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:94:16)
    Emitted 'error' event on Socket instance at:
        at emitErrorNT (node:internal/streams/destroy:169:8)
        at emitErrorCloseNT (node:internal/streams/destroy:128:3)
        at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
      errno: -4060,
      code: 'ENOBUFS',
      syscall: 'write'
    }
    
    Node.js v22.0.0-pre
    node:assert:126
      throw new AssertionError(obj);
      ^
    
    AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
    
    1 !== 0
    
        at ChildProcess.<anonymous> (c:\workspace\node-test-binary-windows-native-suites\node\test\common\benchmark.js:28:12)
        at ChildProcess.emit (node:events:519:28...

Reason parallel/test-blob-file-backed
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/52016/, https://github.com/nodejs/node/pull/52037/)
Appeared test-digitalocean-ubuntu2204_sharedlibs_container-x64-5, test-ibm-ubuntu2204_sharedlibs_container-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/57637/
Last CI https://ci.nodejs.org/job/node-test-pull-request/57664/
Example
not ok 76 parallel/test-blob-file-backed
  ---
  duration_ms: 272.26300
  severity: fail
  exitcode: 1
  stack: |-
    
    node:internal/blob:291
              const error = lazyDOMException('The blob could not be read', 'NotReadableError');
                            ^
    DOMException [NotReadableError]: The blob could not be read
        at BlobReader.<anonymous> (node:internal/blob:291:25)
    
    Node.js v22.0.0-pre
  ...


Reason parallel/test-child-process-exec-timeout-kill
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/51719/, https://github.com/nodejs/node/pull/52027/)
Appeared test-rackspace-win2019_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/57612/
Last CI https://ci.nodejs.org/job/node-test-pull-request/57674/
Example
not ok 100 parallel/test-child-process-exec-timeout-kill
  ---
  duration_ms: 697.00600
  severity: fail
  exitcode: 3221226505
  stack: |-
    
    
    #
    # Fatal error in , line 0
    # Fatal process out of memory: Zone
    #
    #
    #
    #FailureMessage Object: 0000000C265F5B90
    ----- Native stack trace -----
    
  ...


Reason parallel/test-tls-ticket-cluster
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/52002/, https://github.com/nodejs/node/pull/52016/)
Appeared test-azure_msft-win11_vs2022-x64-2, test-ibm-rhel8-s390x-4
First CI https://ci.nodejs.org/job/node-test-pull-request/57609/
Last CI https://ci.nodejs.org/job/node-test-pull-request/57680/
Example
not ok 794 parallel/test-tls-ticket-cluster
  ---
  duration_ms: 570.00400
  severity: fail
  exitcode: 1
  stack: |-
    [primary] got "listening"
    [primary] connecting 64307 session? false
    [primary] got "listening"
    [primary] got "listening"
    [worker] connection reused? false
    [primary] got "not-reused"
    [primary] connecting 64307 session? true
    [worker] connection reused? true
    [primary] got "reused"
    [primary] connecting 64307 session? true
    [worker] connection reused? true
    [primary] got "reused"
    [primary] connecting 64307 session? true
    [worker] connection reused? true
    [primary] got "reused"
    [primary] connecting 64307 session? true
    [worker] connection reused? true
    [primary] got "reused"
    [primary] connecting 64307 session? true
    [primary] got "listening"
    [worker] connection reused? true
    [primary] got "reused"
    [primary] connecting 64307 session? true
    [worker] connection reused? true
    [primary] got "reused"
    [primary] con...

Reason sequential/test-tls-session-timeout
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/51977/, https://github.com/nodejs/node/pull/51996/)
Appeared test-azure_msft-win2016_vs2017-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/57603/
Last CI https://ci.nodejs.org/job/node-test-pull-request/57608/
Example
not ok 956 sequential/test-tls-session-timeout
  ---
  duration_ms: 2480.32100
  severity: fail
  exitcode: 1
  stack: |-
    C:\workspace\node-test-binary-windows-js-suites\node\test\sequential\test-tls-session-timeout.js:114
            throw er;
            ^
    
    [Error: 28110000:error:0A00041A:SSL routines:ssl3_read_bytes:tlsv1 alert decode error:C:\workspace\node-compile-windows\node\deps\openssl\openssl\ssl\record\rec_layer_s3.c:1590:SSL alert number 50
    ] {
      library: 'SSL routines',
      reason: 'tlsv1 alert decode error',
      code: 'ERR_SSL_TLSV1_ALERT_DECODE_ERROR'
    }
    
    Node.js v20.11.2-pre
  ...


Reason wasi/test-wasi
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/52010/, https://github.com/nodejs/node/pull/52028/)
Appeared test-azure_msft-win11_vs2022-x64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/57655/
Last CI https://ci.nodejs.org/job/node-test-pull-request/57656/
Example
not ok 888 wasi/test-wasi
  ---
  duration_ms: 1140.02600
  severity: fail
  exitcode: 1
  stack: |-
    executing cant_dotdot
    (node:6112) ExperimentalWarning: WASI is an experimental feature and might change at any time
    (Use `node --trace-warnings ...` to show where the warning was created)
    fd_prestat_get(3, 69720)
    fd_prestat_dir_name(3, 131088, 8)
    fd_prestat_get(4, 69720)
    fd_prestat_dir_name(4, 131152, 4)
    fd_prestat_get(5, 69720)
    environ_sizes_get(69724, 69720)
    environ_get(138496, 131168)
    fd_fdstat_get(3, 69672)
    path_open(3, 1, 1033, 14, 0, 264240830, 268435455, 0, 69668)
    
    executing clock_getres
    (node:4712) ExperimentalWarning: WASI is an experimental feature and might change at any time
    (Use `node --trace-warnings ...` to show where the warning was created)
    fd_prestat_get(3, 69688)
    fd_prestat_dir_name(3, 131088, 8)
    fd_prestat_get(4, 69688)
    fd_prestat_dir_name(4, 131152, 4)
    fd_prestat_get(5, 69688)
    environ_sizes_get(69692, 6...

Reason wpt/test-url
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/52020/, https://github.com/nodejs/node/pull/52027/)
Appeared test-orka-macos11-x64-2, test-azure_msft-win10_vs2019-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/57645/
Last CI https://ci.nodejs.org/job/node-test-pull-request/57653/
Example
not ok 4135 wpt/test-url
  ---
  duration_ms: 1870.47500
  severity: crashed
  exitcode: -11
  stack: |-
    [SKIPPED] idlharness-shadowrealm.window.js: ShadowRealm support is not enabled
    [SKIPPED] javascript-urls.window.js: requires document.body reference
    [SKIPPED] percent-encoding.window.js: TODO: port from .window.js
    [SKIPPED] url-setters-a-area.window.js?include=file: already tested in url-setters.any.js
    [SKIPPED] url-setters-a-area.window.js?include=javascript: already tested in url-setters.any.js
    [SKIPPED] url-setters-a-area.window.js?include=mailto: already tested in url-setters.any.js
    [SKIPPED] url-setters-a-area.window.js?exclude=(file|javascript|mailto): already tested in url-setters.any.js
    [PASS] ToASCII("fass.de")
    [PASS] ToASCII("faß.de")
    [PASS] ToASCII("Faß.de")
    [PASS] ToASCII("xn--fa-hia.de")
    [PASS] ToASCII("à.א̈")
    [PASS] ToASCII("à.א̈")
    [PASS] ToASCII("À.א̈")
    [PASS] ToASCII("À.א̈")
    [PASS] ToASCII("xn--0ca.xn--ssa73l")
    [PASS] ToA...

Jenkins Failure
CCTest 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 10 (https://github.com/nodejs/node/pull/51866/, https://github.com/nodejs/node/pull/52016/, https://github.com/nodejs/node/pull/52028/, https://github.com/nodejs/node/pull/52010/, https://github.com/nodejs/node/pull/52009/, https://github.com/nodejs/node/pull/51973/, https://github.com/nodejs/node/pull/51972/, https://github.com/nodejs/node/pull/52024/, https://github.com/nodejs/node/pull/52027/, https://github.com/nodejs/node/pull/52037/)
Appeared test-azure_msft-win2016_vs2017-x64-2, test-azure_msft-win2016_vs2017-x64-1, test-azure_msft-win10_vs2019-x64-1, test-azure_msft-win11_vs2022-x64-4, test-azure_msft-win11_vs2022-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/57657/
Last CI https://ci.nodejs.org/job/node-test-pull-request/57696/
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 fatal: No rebase in progress?
Type BUILD_FAILURE
Failed PR 4 (https://github.com/nodejs/node/pull/52002/, https://github.com/nodejs/node/pull/52016/, https://github.com/nodejs/node/pull/52024/, https://github.com/nodejs/node/pull/52040/)
Appeared test-ibm-ubuntu2204_sharedlibs_container-x64-2, test-ibm-ubuntu2204_sharedlibs_container-x64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/57632/
Last CI https://ci.nodejs.org/job/node-test-pull-request/57689/
Example
fatal: No rebase in progress?

Progress
  • parallel/test-domain-error-types (18)
  • parallel/test-debugger-heap-profiler (9)
  • parallel/test-child-process-exec-encoding (3)
  • parallel/test-child-process-exec-maxbuf (3)
  • parallel/test-cluster-fork-stdio (3)
  • sequential/test-worker-fshandles-open-close-on-termination (3)
  • benchmark/test-benchmark-http2 (2)
  • benchmark/test-benchmark-net (2)
  • parallel/test-blob-file-backed (2)
  • parallel/test-child-process-exec-timeout-kill (2)
  • parallel/test-tls-ticket-cluster (2)
  • sequential/test-tls-session-timeout (2)
  • wasi/test-wasi (2)
  • wpt/test-url (2)
  • ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error? (10)
  • fatal: No rebase in progress? (4)

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 reliability report and the linked CI console logs, especially parallel/test-domain-error-types and parallel/test-debugger-heap-profiler. Compare the repeated failures across the listed platforms and PR runs; done means the underlying failures are understood and the affected CI tests no longer produce the reported failures.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, 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
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.