CI Reliability 2025-03-12
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/65593 to node-test-pull-request/65692 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-03-12.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-03-12 00:10 | 0 | 11 | 22 | 6 | 61 | 11.70% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-03-12.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(6) -
Failed to create a temp file on C:\workspace\node-compile-windows(3) -
error: remote GitHub already exists.(5) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(3) -
Error: list index out of range(3) -
error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj](3) -
error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\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_compiler_host.vcxproj](2) -
sequential/test-fs-watch(10) -
parallel/test-fs-watch-recursive-delete(9) -
parallel/test-runner-run-watch(8) -
parallel/test-buffer-tostring-rangeerror(7) -
parallel/test-debugger-heap-profiler(5) -
parallel/test-file-write-stream4(4) -
parallel/test-runner-output(3) -
parallel/test-debugger-break(2) -
parallel/test-zlib-brotli-16GB(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-12.md and the linked node-test-pull-request jobs, then inspect the listed failures and named tests such as sequential/test-fs-watch and parallel/test-runner-run-watch. Compare recurring failures with the generated ncu-ci report; done means the reported reliability problems are addressed and the affected CI runs no longer reproduce them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github, node.js, 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