CI Reliability 2025-12-30
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/70529 to node-test-pull-request/70628 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-12-30.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-12-30 00:12 | 0 | 11 | 31 | 10 | 48 | 12.22% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-12-30.md to see failure details
Progress
-
parallel/test-repl-programmatic-history(7) -
parallel/test-quic-test-client(4) -
sequential/test-performance-eventloopdelay(3) -
async-hooks/test-emit-after-on-destroyed(2) -
test-runner/test-run-watch-dependency-repeatedly(2) -
test-runner/test-run-watch-run-duration(2) -
Build timed out (after 30 minutes). Marking the build as failed.(3) -
ERROR: Error fetching remote repo 'origin'(4) -
Failed to trigger node-test-commit(3) -
Failed to trigger sub builds(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 linked CI build range and the report at reports/2025-12-30.md, then review the listed failing tests and infrastructure errors. Determine which failures can be reproduced and addressed; done means the reported failures no longer recur in the affected CI runs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100