CI Reliability 2025-12-28
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/70514 to node-test-pull-request/70603 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-12-28.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-12-28 00:14 | 0 | 10 | 29 | 10 | 51 | 11.11% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-12-28.md to see failure details
Progress
-
parallel/test-repl-programmatic-history(6) -
parallel/test-quic-test-client(5) -
sequential/test-performance-eventloopdelay(5) -
test-runner/test-run-watch-without-file(3) -
wpt/test-hr-time(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 60 minutes). Marking the build as failed.(3) -
Build timed out (after 30 minutes). Marking the build as failed.(2) -
ERROR: Error fetching remote repo 'origin'(6) -
Failed to trigger node-test-commit(2) -
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 reports/2025-12-28.md and the linked node-test-pull-request builds generated by ncu-ci walk pr --stats=true --markdown reports/2025-12-28.md. Review the listed test and build failures, then use the Progress checklist to track investigation. Done means the identified recurring failures are addressed and the relevant CI runs no longer reproduce them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- ci-cd, devops, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100