CI Reliability 2025-11-05
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/69951 to node-test-pull-request/70050 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-11-05.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-11-05 00:12 | 1 | 27 | 12 | 1 | 59 | 27.55% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-11-05.md to see failure details
Progress
-
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max(11) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-hex(9) -
parallel/test-perf-hooks-timerify(9) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-2(7) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-utf8(6) -
parallel/test-watch-mode-kill-signal-override(6) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-ascii(5) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-base64(5) -
parallel/test-quic-test-client(4) -
parallel/test-watch-mode-files_watcher(3) -
sequential/test-worker-prof(3) -
wpt/test-hr-time(3) -
client-proxy/test-https-proxy-request-invalid-char-in-url(2) -
wasi/test-wasi-pthread(2) -
wpt/test-streams(2) -
Unexpected termination of the channel(3) -
Build timed out (after 30 minutes). Marking the build as failed.(2) -
error: remote GitHub already exists.(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-11-05.md and the linked CI runs to investigate the listed recurring failures, including the named addons, parallel, sequential, and WPT tests. Review the failure details and determine the relevant fixes; done means the listed failures are resolved and the affected pull-request CI runs return successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, 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
- 25/100