CI Reliability 2025-04-20
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/66276 to node-test-pull-request/66372 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-04-20.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-04-20 00:12 | 1 | 5 | 33 | 8 | 53 | 5.49% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-04-20.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(4) -
error C1060: compiler is out of heap space [C:\workspace\node-compile-windows-debug\node\tools\v8_gypfiles\v8_turboshaft.vcxproj](3) -
error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj](3) -
fatal: No rebase in progress?(3) -
Failed to trigger node-test-commit(2) -
fatal error: Killed signal terminated program cc1plus(2) -
parallel/test-file-write-stream4(6) -
sequential/test-performance-eventloopdelay(3) -
parallel/test-buffer-tostring-rangeerror(2) -
parallel/test-debugger-break(2) -
parallel/test-debugger-heap-profiler(2) -
parallel/test-runner-output(2) -
parallel/test-runner-run-watch(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 node-test-pull-request builds and the generated report at reports/2025-04-20.md; review how ncu-ci walk pr --stats=true --markdown produced the failure groups. Determine which listed failures still reproduce and document or address the causes so the affected CI checks become reliable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, 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