CI Reliability 2025-11-11
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/70037 to node-test-pull-request/70133 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-11-11.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-11-11 00:12 | 2 | 22 | 19 | 2 | 55 | 22.92% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-11-11.md to see failure details
Progress
-
Unexpected termination of the channel(4) -
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:(5) -
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-by-1-utf8(4) -
parallel/test-quic-test-client(4) -
parallel/test-repl-paste-big-data(4) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max(3) -
async-hooks/test-improper-unwind(3) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-2(2) -
async-hooks/test-emit-after-on-destroyed(2) -
parallel/test-internal-util-construct-sab(2) -
parallel/test-perf-hooks-timerify(2) -
parallel/test-watch-mode-kill-signal-default(2) -
parallel/test-worker-nearheaplimit-deadlock(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
Open reports/2025-11-11.md and review the linked Jenkins jobs from node-test-pull-request/70037 through 70133. Start with the recurring failures listed in the Progress section, then trace their failure details and update the checklist as each issue is addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100