CI Reliability 2025-03-23
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/65785 to node-test-pull-request/65884 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-03-23.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-03-23 00:11 | 0 | 2 | 24 | 10 | 64 | 2.22% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-03-23.md to see failure details
Progress
-
error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj](6) -
Failed to trigger node-test-commit(5) -
Error: list index out of range(4) -
error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_turboshaft.vcxproj](4) -
error: remote GitHub already exists.(4) -
fatal error: Killed signal terminated program cc1plus(3) -
error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_base_without_compiler.vcxproj](2) -
sh: line 12: [: -gt: unary operator expected(2) -
pummel/test-buffer-large-size(14) -
parallel/test-stream-readable-unpipe-resume(3) -
parallel/test-buffer-tostring-rangeerror(2) -
parallel/test-file-write-stream4(2) -
parallel/test-runner-run-watch(2) -
parallel/test-zlib-convenience-methods(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-23.md, linked from the issue, and inspect the Jenkins job range node-test-pull-request/65785 through 65884. Triage the listed compiler, trigger, remote, shell, and test failures; done means the recurring failures are resolved and the affected CI runs no longer reproduce them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- 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