CI Reliability 2025-05-10
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/66638 to node-test-pull-request/66736 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-05-10.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-05-10 00:10 | 0 | 11 | 20 | 4 | 65 | 11.46% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-05-10.md to see failure details
Progress
-
Build timed out (after 60 minutes). Marking the build as failed.(12) -
Build timed out (after 30 minutes). Marking the build as failed.(8) -
Backing channel 'JNLP4-connect connection from ... is disconnected.(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(8) -
parallel/test-cluster-fork-stdio(8) -
parallel/test-runner-run-watch(4) -
sequential/test-performance-eventloopdelay(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) -
pummel/test-timers(2) -
sequential/test-tls-session-timeout(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 by reading reports/2025-05-10.md and the linked CI jobs for the reported failures. Compare the timeout, infrastructure, build, and test failures listed in Progress, then investigate the affected Node.js tests and build triggers. Done means identifying and addressing the reported reliability failures and updating the progress items with verified results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, 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
- 25/100