CI Reliability 2025-11-20
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/70156 to node-test-pull-request/70251 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-11-20.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-11-20 00:11 | 0 | 29 | 20 | 4 | 47 | 30.21% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-11-20.md to see failure details
Progress
-
Backing channel 'JNLP4-connect connection from ... is disconnected.(4) -
Build timed out (after 30 minutes). Marking the build as failed.(2) -
Build timed out (after 60 minutes). Marking the build as failed.(2) -
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) -
fatal: unable to access 'https://github.com/nodejs/build.git/': The requested URL returned error: 500(2) -
sequential/test-performance-eventloopdelay(3) -
test-runner/test-run-watch-run-duration(3) -
client-proxy/test-https-proxy-request-invalid-char-in-url(2) -
parallel/test-quic-test-client(2) -
parallel/test-repl-paste-big-data(2) -
parallel/test-repl-programmatic-history(2) -
test-runner/test-run-watch-emit-restarted(2) -
test-runner/test-run-watch-repeatedly(2) -
test-runner/test-run-watch-without-file(2) -
wpt/test-hr-time(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
Read reports/2025-11-20.md and the generated failure list first, then inspect the linked node-test-pull-request jobs from 70156 through 70251. Group the repeated infrastructure and test failures, trace each to its owning area, and verify that the affected CI jobs no longer reproduce the reported failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- 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