CI Reliability 2025-11-15
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/70078 to node-test-pull-request/70175 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-11-15.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-11-15 00:11 | 2 | 21 | 26 | 3 | 48 | 22.11% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-11-15.md to see failure details
Progress
-
Backing channel 'JNLP4-connect connection from ... is disconnected.(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:(5) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(2) -
fatal: no rebase in progress(2) -
parallel/test-perf-hooks-timerify-histogram-sync(5) -
parallel/test-repl-paste-big-data(5) -
async-hooks/test-improper-unwind(2) -
parallel/test-internal-util-construct-sab(2) -
parallel/test-quic-test-client(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
Start with reports/2025-11-15.md and the linked node-test-pull-request jobs, then inspect logs for the listed failure signatures and test names. Done means the repeated failures in the Progress list have been investigated and the corresponding checklist items are updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, node.js, 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