CI Reliability 2025-01-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/64631 to node-test-pull-request/64725 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-01-25.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-01-25 00:09 | 2 | 11 | 15 | 19 | 53 | 13.92% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-01-25.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(5) -
Build timed out (after 60 minutes). Marking the build as failed.(3) -
ERROR: Error fetching remote repo 'origin'(3) -
fatal: No rebase in progress?(7) -
Error: invalid syntax(5) -
error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj](2) -
parallel/test-permission-fs-read(16) -
parallel/test-permission-fs-write(16) -
parallel/test-fs-cp(12) -
parallel/test-cluster-fork-stdio(9) -
parallel/test-cluster-concurrent-disconnect(8) -
parallel/test-cluster-disconnect-unshared-tcp(8) -
parallel/test-net-write-fully-async-buffer(6) -
es-module/test-wasm-web-api(5) -
parallel/test-without-async-context-frame(5) -
parallel/test-net-write-fully-async-hex-string(4) -
parallel/test-buffer-tostring-rangeerror(3) -
es-module/test-esm-loader-entry-url(2) -
parallel/test-buffer-tostring-range(2) -
parallel/test-fs-watch-recursive-delete(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-01-25.md and the linked node-test-pull-request builds covering 64631 through 64725. Review the listed timeout, repository, Windows compiler, and test failures, then use the Progress checklist to track which recurring failures have been investigated and resolved.
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
- 25/100