CI Reliability 2025-11-17
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/70110 to node-test-pull-request/70205 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-11-17.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-11-17 00:11 | 0 | 21 | 26 | 4 | 49 | 21.88% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-11-17.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:(4) -
ERROR: Error fetching remote repo 'origin'(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 error: Killed signal terminated program cc1plus(2) -
parallel/test-repl-paste-big-data(4) -
async-hooks/test-improper-unwind(2) -
client-proxy/test-https-proxy-request-invalid-char-in-url(2) -
parallel/test-perf-hooks-timerify-histogram-sync(2) -
parallel/test-quic-test-client(2) -
sequential/test-performance-eventloopdelay(2) -
test-runner/test-run-watch-emit-restarted(2) -
test-runner/test-run-watch-repeatedly(2) -
test-runner/test-run-watch-run-duration(2) -
wpt/test-webcrypto(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
Review reports/2025-11-17.md and the linked Jenkins runs from node-test-pull-request/70110 through 70205, starting with the failure groups listed under Progress. Work through the repeated infrastructure and test failures, with completion indicated when the listed reliability problems have been addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100