nodejs / nodejs/reliability

CI Reliability 2025-03-20

Open
#1,148 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/65743 to node-test-pull-request/65842 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-03-20.md)

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2025-03-20 00:10 0 2 29 4 65 2.08%

Open https://github.com/nodejs/reliability/blob/main/reports/2025-03-20.md to see failure details

Progress
  • Build timed out (after 30 minutes). Marking the build as failed. (4)
  • fatal error: Killed signal terminated program cc1plus (8)
  • error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj] (6)
  • error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_turboshaft.vcxproj] (6)
  • error: remote GitHub already exists. (4)
  • Error: - process terminated with status 1, expected 0 (3)
  • Error: list index out of range (3)
  • ERROR: Step ‘Record fingerprints of files to track usage’ failed: no workspace for ... (2)
  • error C1060: compiler is out of heap space [C:\workspace\node-compile-windows-debug\node\tools\v8_gypfiles\v8_turboshaft.vcxproj] (2)
  • error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_base_without_compiler.vcxproj] (2)
  • error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_turboshaft_host.vcxproj] (2)
  • fatal: No rebase in progress? (2)
  • pummel/test-buffer-large-size (11)
  • parallel/test-stream-readable-unpipe-resume (4)
  • node-api/test_threadsafe_function/test (3)
  • parallel/test-buffer-tostring-rangeerror (3)
  • parallel/test-runner-run-watch (2)
  • parallel/test-zlib-convenience-methods (2)
  • sequential/test-perf-hooks (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 by reading reports/2025-03-20.md and the linked CI runs from node-test-pull-request/65743 through 65842. Use the listed failure categories and the ncu-ci walk command as the investigation entry point; done would require addressing the reported CI failures and verifying that the affected PR runs become reliable.

Written by the indexing model from the issue text.

Assessment

Tech stack
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.