CI Reliability 2025-11-07
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/69980 to node-test-pull-request/70080 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-11-07.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-11-07 00:12 | 1 | 28 | 12 | 2 | 57 | 28.87% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-11-07.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: Error fetching remote repo 'origin'(2) -
error: remote GitHub already exists.(2) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max(10) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-hex(7) -
parallel/test-perf-hooks-timerify(6) -
parallel/test-quic-test-client(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-utf8(5) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-2(5) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-base64(4) -
parallel/test-perf-hooks-timerify-histogram-sync(4) -
wpt/test-hr-time(4) -
parallel/test-watch-mode-files_watcher(3) -
parallel/test-watch-mode-kill-signal-override(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) -
sequential/test-worker-prof(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-07.md and the linked node-test-pull-request jobs to inspect details for the repeated failures listed in the issue. Prioritize a failure category or test with multiple occurrences, reproduce it in the relevant CI job, and consider the work complete when its cause is understood and the corresponding progress item can be resolved.
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
- 30/100