CI Reliability 2025-11-06
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/69963 to node-test-pull-request/70062 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-11-06.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-11-06 00:11 | 0 | 27 | 13 | 2 | 58 | 27.55% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-11-06.md to see failure details
Progress
-
Unexpected termination of the channel(3) -
Build timed out (after 30 minutes). Marking the build as failed.(2) -
error: remote GitHub already exists.(2) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max(11) -
parallel/test-perf-hooks-timerify(10) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-hex(9) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-2(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) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-utf8(5) -
parallel/test-quic-test-client(5) -
parallel/test-watch-mode-kill-signal-override(4) -
parallel/test-watch-mode-files_watcher(3) -
wpt/test-hr-time(3) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-binary(2) -
client-proxy/test-https-proxy-request-invalid-char-in-url(2) -
parallel/test-fastutf8stream-destroy(2) -
parallel/test-perf-hooks-timerify-histogram-sync(2) -
sequential/test-worker-prof(2) -
wasi/test-wasi-pthread(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-11-06.md and the linked node-test-pull-request jobs, using the ncu-ci walk pr report to inspect the recurring failures. Focus would need to be agreed for one or more listed tests or CI errors, with completion shown by the relevant failures no longer recurring in CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- 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