CI Reliability 2025-11-13
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/70056 to node-test-pull-request/70152 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-11-13.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-11-13 00:11 | 1 | 23 | 25 | 2 | 49 | 23.71% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-11-13.md to see failure details
Progress
-
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(7) -
parallel/test-quic-test-client(4) -
parallel/test-repl-paste-big-data(4) -
async-hooks/test-improper-unwind(3) -
parallel/test-internal-util-construct-sab(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-13.md and the linked node-test-pull-request runs 70056–70152; inspect the listed Git, JUnit, and named Node.js test failures. Reproduce a recurring failure, then confirm the affected test or CI step passes in a rerun.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, nodejs, 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
- 30/100