CI Reliability 2025-05-16
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/66731 to node-test-pull-request/66829 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-05-16.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-05-16 00:11 | 0 | 13 | 24 | 3 | 60 | 13.40% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-05-16.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'(4) -
fatal: No rebase in progress?(4) -
Failed to trigger node-test-commit(2) -
pummel/test-blob-slice-with-large-size(11) -
sequential/test-tls-session-timeout(6) -
parallel/test-buffer-tostring-range(5) -
parallel/test-cluster-fork-stdio(5) -
parallel/test-crypto-async-sign-verify(4) -
parallel/test-buffer-tostring-rangeerror(3) -
parallel/test-stream-readable-to-web(3) -
sequential/test-performance-eventloopdelay(3) -
parallel/test-async-context-frame(2) -
parallel/test-esm-loader-hooks-inspect-wait(2) -
parallel/test-http-get-pipeline-problem(2) -
parallel/test-http-server-headers-timeout-keepalive(2) -
parallel/test-runner-run-watch(2) -
parallel/test-worker-nearheaplimit-deadlock(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-16.md and the linked node-test-pull-request jobs, using ncu-ci walk pr --stats=true --markdown reports/2025-05-16.md as the report entry point. Review the repeated timeout, repository, orchestration, and test failures listed in the Progress section; done means the identified CI failures are addressed and the affected jobs no longer reproduce them.
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