CI Reliability 2025-01-27
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/64665 to node-test-pull-request/64762 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-01-27.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-01-27 00:10 | 0 | 15 | 16 | 9 | 60 | 16.48% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-01-27.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(6) -
Build timed out (after 60 minutes). Marking the build as failed.(2) -
ERROR: Error fetching remote repo 'origin'(3) -
fatal: No rebase in progress?(5) -
Error: invalid syntax(4) -
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(17) -
parallel/test-permission-fs-write(17) -
parallel/test-fs-cp(12) -
parallel/test-cluster-fork-stdio(9) -
parallel/test-cluster-concurrent-disconnect(8) -
es-module/test-wasm-web-api(6) -
parallel/test-cluster-disconnect-unshared-tcp(6) -
parallel/test-without-async-context-frame(6) -
parallel/test-net-write-fully-async-buffer(4) -
parallel/test-buffer-tostring-rangeerror(3) -
parallel/test-net-write-fully-async-hex-string(3) -
parallel/test-esm-loader-hooks-inspect-wait(2) -
parallel/test-file-write-stream4(2) -
parallel/test-fs-watch-recursive-delete(2) -
parallel/test-watch-mode-files_watcher(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-27.md and the linked node-test-pull-request runs, then group the repeated failures listed in the Progress checklist. Inspect the affected test names and error messages first; the work is done when the listed CI reliability failures have been addressed and the checklist reflects their status.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- 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
- 30/100