CI Reliability 2025-03-19
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/65733 to node-test-pull-request/65832 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-03-19.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-03-19 00:10 | 1 | 2 | 26 | 3 | 68 | 2.08% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-03-19.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.(6) -
ERROR: Step ‘Record fingerprints of files to track usage’ failed: no workspace for ...(4) -
Error: - process terminated with status 1, expected 0(3) -
error C1060: compiler is out of heap space [C:\workspace\node-compile-windows-debug\node\tools\v8_gypfiles\v8_turboshaft.vcxproj](3) -
Error: list index out of range(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(5) -
parallel/test-buffer-tostring-rangeerror(4) -
node-api/test_threadsafe_function/test(3) -
parallel/test-runner-run-watch(2) -
parallel/test-zlib-convenience-methods(2) -
sequential/test-perf-hooks(2)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked reports/2025-03-19.md failure details and the node-test-pull-request Jenkins runs listed in the issue. Use the ncu-ci walk pr --stats=true --markdown reports/2025-03-19.md output to group the compiler, timeout, infrastructure, and test failures; done means the reported recurring failures have been investigated and the progress items can be resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, 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