CI Reliability 2025-11-08
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/69992 to node-test-pull-request/70092 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-11-08.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-11-08 00:10 | 0 | 31 | 13 | 3 | 53 | 31.96% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-11-08.md to see failure details
Progress
-
Unexpected termination of the channel(4) -
ERROR: Error fetching remote repo 'origin'(2) -
error: remote GitHub already exists.(2) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max(8) -
parallel/test-perf-hooks-timerify-histogram-sync(5) -
parallel/test-quic-test-client(5) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-ascii(4) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-utf8(4) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-2(4) -
parallel/test-perf-hooks-timerify(4) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-base64(3) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-hex(3) -
parallel/test-watch-mode-kill-signal-override(3) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-binary(2) -
parallel/test-fastutf8stream-destroy(2) -
sequential/test-worker-prof(2) -
wpt/test-hr-time(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-08.md and the linked node-test-pull-request jobs, then group the repeated failures listed under Progress. Investigate each affected CI or test item and address its cause; done means the listed failures are resolved and the CI is green.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100