CI Reliability 2025-03-25
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/65789 to node-test-pull-request/65887 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-03-25.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-03-25 00:10 | 0 | 2 | 25 | 10 | 63 | 2.22% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-03-25.md to see failure details
Progress
-
Failed to trigger node-test-commit(5) -
error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj](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(2) -
sh: line 12: [: -gt: unary operator expected(2) -
pummel/test-buffer-large-size(12) -
parallel/test-buffer-tostring-rangeerror(2) -
parallel/test-file-write-stream4(2) -
parallel/test-runner-run-watch(2) -
parallel/test-stream-readable-unpipe-resume(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 by reviewing reports/2025-03-25.md and the linked node-test-pull-request jobs from 65789 through 65887. Use the generated failure details to identify which unchecked failures are actionable, then verify that the relevant CI failures are resolved and update the Progress list.
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
- 35/100