CI Reliability 2025-11-10
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/70026 to node-test-pull-request/70121 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-11-10.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-11-10 00:12 | 6 | 22 | 19 | 2 | 51 | 23.91% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-11-10.md to see failure details
Progress
-
Unexpected termination of the channel(4) -
Build timed out (after 30 minutes). Marking the build as failed.(2) -
Command "git fetch --no-tags --force --progress -- git@github.com:nodejs/node.git +refs/heads/*:refs/remotes/origin/* +refs/heads/v20.x-staging:refs/remotes/origin/_jenkins_local_branch" returned status code 128:(3) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(2) -
fatal: No rebase in progress?(2) -
fatal: no rebase in progress(2) -
parallel/test-perf-hooks-timerify-histogram-sync(8) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max(4) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-utf8(4) -
parallel/test-quic-test-client(3) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-hex(2) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-2(2) -
async-hooks/test-emit-after-on-destroyed(2) -
async-hooks/test-improper-unwind(2) -
parallel/test-fastutf8stream-destroy(2) -
parallel/test-internal-util-construct-sab(2) -
parallel/test-perf-hooks-timerify(2) -
parallel/test-repl-paste-big-data(2) -
parallel/test-watch-mode-kill-signal-default(2) -
parallel/test-watch-mode-kill-signal-override(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-10.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 failures, including the named parallel, addons, and async-hooks tests, and trace each failure to its cause. Done means the reported CI failures are addressed and the corresponding progress items can be checked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, shell
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100