CI Reliability 2025-11-16
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/70088 to node-test-pull-request/70186 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-11-16.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-11-16 00:12 | 1 | 17 | 27 | 3 | 52 | 17.71% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-11-16.md to see failure details
Progress
-
Backing channel 'JNLP4-connect connection from ... is disconnected.(4) -
Build timed out (after 60 minutes). Marking the build as failed.(3) -
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) -
fatal error: Killed signal terminated program cc1plus(3) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(2) -
ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ...(2) -
ERROR: Step ‘Record fingerprints of files to track usage’ failed: no workspace for ...(2) -
fatal: no rebase in progress(2) -
parallel/test-repl-paste-big-data(5) -
parallel/test-perf-hooks-timerify-histogram-sync(4) -
async-hooks/test-improper-unwind(2) -
parallel/test-internal-util-construct-sab(2) -
parallel/test-quic-test-client(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-16.md and the linked node-test-pull-request jobs 70088–70186, then review the listed CI and Node.js test failures. Done means determining actionable causes for the repeated failures and addressing or documenting each selected item in the Progress list.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, 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