CI Reliability 2025-05-11
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/66649 to node-test-pull-request/66747 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-05-11.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-05-11 00:12 | 2 | 11 | 22 | 5 | 60 | 11.83% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-05-11.md to see failure details
Progress
-
Build timed out (after 60 minutes). Marking the build as failed.(8) -
Build timed out (after 30 minutes). Marking the build as failed.(7) -
Backing channel 'JNLP4-connect connection from ... is disconnected.(2) -
Build timed out (after 15 minutes). Marking the build as failed.(2) -
ERROR: Error fetching remote repo 'origin'(2) -
fatal error: Killed signal terminated program cc1plus(7) -
Failed to trigger node-test-commit(3) -
fatal: No rebase in progress?(3) -
Failed to trigger sub builds(2) -
parallel/test-buffer-tostring-rangeerror(7) -
parallel/test-cluster-fork-stdio(7) -
parallel/test-runner-run-watch(3) -
sequential/test-performance-eventloopdelay(3) -
sequential/test-tls-session-timeout(3) -
parallel/test-net-autoselectfamily(2) -
parallel/test-net-listen-ipv6only(2) -
parallel/test-runner-run(2) -
parallel/test-without-async-context-frame(2) -
pummel/test-heapdump-zlib(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-05-11.md in the nodejs/reliability repository and the linked CI runs covering builds 66649–66747; the report was generated with ncu-ci walk pr --stats=true --markdown reports/2025-05-11.md. Review the listed timeout, infrastructure, and test failures, but the issue does not define a specific change or completion condition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100