CI Reliability 2025-01-26
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/64654 to node-test-pull-request/64750 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-01-26.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-01-26 00:10 | 0 | 14 | 17 | 12 | 57 | 15.91% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-01-26.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.(3) -
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(16) -
parallel/test-permission-fs-write(16) -
parallel/test-fs-cp(13) -
parallel/test-cluster-concurrent-disconnect(9) -
parallel/test-cluster-fork-stdio(9) -
parallel/test-cluster-disconnect-unshared-tcp(8) -
parallel/test-without-async-context-frame(6) -
es-module/test-wasm-web-api(5) -
parallel/test-net-write-fully-async-buffer(4) -
parallel/test-net-write-fully-async-hex-string(4) -
es-module/test-esm-loader-entry-url(2) -
parallel/test-buffer-tostring-rangeerror(2) -
parallel/test-esm-loader-hooks-inspect-wait(2) -
parallel/test-file-write-stream4(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-26.md and the node-test-pull-request jobs 64654 through 64750, using the listed failure messages and test names to group recurring failures. Review how the report was generated with ncu-ci walk pr --stats=true --markdown reports/2025-01-26.md; done means the recurring failures in the Progress checklist have documented resolutions or are otherwise cleared.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100