CI Reliability 2025-09-23
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/69232 to node-test-pull-request/69331 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-09-23.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-09-23 00:10 | 0 | 17 | 35 | 8 | 40 | 18.48% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-09-23.md to see failure details
Progress
-
Build timed out (after 60 minutes). Marking the build as failed.(6) -
Build timed out (after 30 minutes). Marking the build as failed.(5) -
Unexpected termination of the channel(2) -
Failed to trigger node-test-commit(3) -
parallel/test-runner-watch-mode-kill-signal(4) -
parallel/test-runner-run-watch(3) -
parallel/test-http2-close-while-writing(2) -
parallel/test-worker-nearheaplimit-deadlock(2) -
wpt/test-streams(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-09-23.md and the linked node-test-pull-request jobs, using the generated ncu-ci walk pr --stats=true --markdown command as context. Review the listed timeout, channel, trigger, and test failures, then use the report details to determine whether each item is resolved and update the progress checklist when the corresponding CI failures no longer recur.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, shell
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100