CI Reliability 2025-12-20
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/70438 to node-test-pull-request/70535 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-12-20.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-12-20 00:12 | 2 | 10 | 17 | 4 | 67 | 10.64% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-12-20.md to see failure details
Progress
-
Backing channel 'JNLP4-connect connection from ... is disconnected.(3) -
Build timed out (after 30 minutes). Marking the build as failed.(3) -
Build timed out (after 60 minutes). Marking the build as failed.(2) -
Unexpected termination of the channel(2) -
ERROR: Error fetching remote repo 'origin'(10) -
Failed to trigger node-test-commit(3) -
fatal: No rebase in progress?(2) -
parallel/test-repl-programmatic-history(6) -
parallel/test-quic-test-client(5) -
parallel/test-runner-run(5) -
sequential/test-performance-eventloopdelay(4) -
test-runner/test-run-watch-without-file(4) -
wpt/test-hr-time(4) -
test-runner/test-run-watch-emit-restarted(3) -
test-runner/test-run-watch-run-duration(3) -
async-hooks/test-improper-order(2) -
node-api/test_worker_buffer_callback/test-free-called(2) -
parallel/test-http2-close-while-writing(2) -
wpt/test-wasm-webapi(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-12-20.md and the linked node-test-pull-request builds, using the listed failure messages and test names as entry points. Determine which failures are actionable and reproduce them in the CI workflow or corresponding tests; done means the recurring failures are addressed and the affected pull requests can complete reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- 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