nodejs / nodejs/reliability

CI Reliability 2025-04-17

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2025-04-17 00:11 2 1 29 8 60 1.11%

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

Progress
  • parallel/test-file-write-stream4 (6)
  • parallel/test-runner-plan (6)
  • sequential/test-tls-session-timeout (4)
  • parallel/test-debugger-break (3)
  • parallel/test-debugger-heap-profiler (3)
  • sequential/test-performance-eventloopdelay (3)
  • parallel/test-buffer-tostring-rangeerror (2)
  • Build timed out (after 30 minutes). Marking the build as failed. (4)
  • Build timed out (after 60 minutes). Marking the build as failed. (2)
  • Error: list index out of range (11)
  • error C2065: 'NoArrayBufferZeroFillScope': undeclared identifier [C:\workspace\node-compile-windows\node\libnode.vcxproj] (10)
  • error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj] (7)
  • error: remote GitHub already exists. (5)
  • error C1060: compiler is out of heap space [C:\workspace\node-compile-windows-debug\node\tools\v8_gypfiles\v8_turboshaft.vcxproj] (4)
  • ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (2)
  • ERROR: The process with PID 9828 (child process of PID 10148) could not be terminated. (2)
  • Failed to trigger node-test-commit (2)
  • error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers_host.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)

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 reports/2025-04-17.md and the linked node-test-pull-request jobs to inspect the listed recurring failures. Trace one failure to its underlying cause and identify the relevant change or configuration area. Done means the selected CI failure is resolved or explained and its Progress entry can be updated.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.