CI Reliability 2025-06-24
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/67526 to node-test-pull-request/67627 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-06-24.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-06-24 00:11 | 0 | 1 | 23 | 6 | 70 | 1.06% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-06-24.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(11) -
Backing channel 'JNLP4-connect connection from ... is disconnected.(2) -
Build timed out (after 60 minutes). Marking the build as failed.(2) -
ERROR: Error fetching remote repo 'origin'(4) -
Error: - process terminated with status 1, expected 0(8) -
fatal: No rebase in progress?(3) -
parallel/test-config-file(17) -
pummel/test-string-decoder-large-buffer(15) -
parallel/test-buffer-tostring-range(10) -
pummel/test-buffer-large-size-buffer-alloc-unsafe(9) -
pummel/test-buffer-large-size-buffer-write(8) -
parallel/test-npm-install(6) -
sequential/test-performance-eventloopdelay(6) -
parallel/test-worker-nearheaplimit-deadlock(3) -
pummel/test-buffer-large-size-buffer-alloc(3) -
wpt/test-streams(3) -
es-module/test-vm-contextified-script-leak(2) -
parallel/test-esm-loader-hooks-inspect-wait(2) -
parallel/test-net-autoselectfamily(2) -
parallel/test-net-listen-ipv6only(2) -
parallel/test-runner-run-watch(2) -
parallel/test-stream-readable-to-web(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 with the generated report at reports/2025-06-24.md and the linked node-test-pull-request builds. Review the repeated timeout, repository-fetch, and named test failures to determine which failure is actionable; the issue does not specify a particular fix or completion criterion.
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