CI Reliability 2025-03-22
Open
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/65779 to node-test-pull-request/65878 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-03-22.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-03-22 00:10 | 0 | 2 | 24 | 10 | 64 | 2.22% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-03-22.md to see failure details
Progress
-
fatal error: Killed signal terminated program cc1plus(7) -
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](5) -
Error: list index out of range(4) -
error: remote GitHub already exists.(4) -
Failed to trigger node-test-commit(3) -
error C1060: compiler is out of heap space [C:\workspace\node-compile-windows-debug\node\tools\v8_gypfiles\v8_compiler.vcxproj](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) -
pummel/test-buffer-large-size(14) -
parallel/test-stream-readable-unpipe-resume(3) -
node-api/test_threadsafe_function/test(2) -
parallel/test-buffer-tostring-rangeerror(2) -
parallel/test-file-write-stream4(2) -
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 reports/2025-03-22.md and the linked node-test-pull-request runs, then inspect the repeated compiler, trigger, and test failures listed in the Progress section. Done means investigating and resolving the listed CI failures and updating the progress checklist with the results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100