CI Reliability 2025-03-14
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/65630 to node-test-pull-request/65728 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-03-14.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-03-14 00:10 | 0 | 12 | 18 | 2 | 68 | 12.24% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-03-14.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(3) -
Failed to create a temp file on C:\workspace\node-compile-windows(3) -
error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj](8) -
error: remote GitHub already exists.(8) -
error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_turboshaft.vcxproj](4) -
error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_compiler_host.vcxproj](3) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(2) -
ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error?(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_initializers_host.vcxproj](2) -
sequential/test-fs-watch(10) -
parallel/test-fs-watch-recursive-delete(9) -
parallel/test-buffer-tostring-rangeerror(6) -
parallel/test-file-write-stream4(5) -
parallel/test-debugger-heap-profiler(4) -
parallel/test-runner-run-watch(4) -
sequential/test-performance-eventloopdelay(3) -
parallel/test-debugger-break(2) -
parallel/test-runner-output(2) -
sequential/test-vm-timeout-escape-promise-module-2(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-14.md and the linked node-test-pull-request builds, using the ncu-ci walk pr --stats=true --markdown command as the report entry point. Review the listed timeout, Windows compiler, remote GitHub, JUnit-report, and named test failures; done means the recurring CI failures are resolved and the reported reliability improves.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100