nodejs / nodejs/reliability

CI Reliability 2025-03-21

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2025-03-21 00:10 3 2 30 6 59 2.20%

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

Progress
  • Build timed out (after 30 minutes). Marking the build as failed. (2)
  • 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] (7)
  • error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_turboshaft.vcxproj] (5)
  • Error: list index out of range (4)
  • error: remote GitHub already exists. (4)
  • 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\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 (12)
  • parallel/test-stream-readable-unpipe-resume (4)
  • node-api/test_threadsafe_function/test (2)
  • parallel/test-buffer-tostring-rangeerror (2)
  • 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 with the linked node-test-pull-request Jenkins runs and the reliability report at reports/2025-03-21.md. Review the listed timeout, compiler, Git, and test failures, then determine which failures remain reproducible. Done means the reported CI failures are addressed and subsequent pull-request runs no longer show them.

Written by the indexing model from the issue text.

Assessment

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