CI Reliability 2025-02-15
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/65107 to node-test-pull-request/65204 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-02-15.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-02-15 00:09 | 0 | 20 | 11 | 8 | 61 | 21.74% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-02-15.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(7) -
ERROR: Error fetching remote repo 'origin'(2) -
sh: line 9: [: -gt: unary operator expected(7) -
fatal: detected dubious ownership in repository at 'C:/workspace/node-test-binary-windows-native-suites/build'(5) -
fatal: No rebase in progress?(4) -
error: remote GitHub already exists.(2) -
parallel/test-assert-fail(14) -
parallel/test-runner-run-watch(10) -
benchmark/test-benchmark-http2(6) -
parallel/test-file-write-stream4(6) -
parallel/test-buffer-tostring-rangeerror(4) -
sequential/test-perf-hooks(3) -
parallel/test-net-write-fully-async-buffer(2) -
parallel/test-net-write-fully-async-hex-string(2) -
parallel/test-stream-readable-unpipe-resume(2) -
sequential/test-gc-http-client(2) -
sequential/test-tls-session-timeout(2) -
wpt/test-compression(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-02-15.md and the linked CI runs, then inspect the listed timeout, Git, shell, and test failures. The report was generated with ncu-ci walk pr --stats=true --markdown reports/2025-02-15.md; the issue does not name a target file, specific fix, or completion condition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, shell
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100