CI Reliability 2025-09-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/69143 to node-test-pull-request/69239 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-09-16.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-09-16 00:10 | 0 | 15 | 22 | 8 | 55 | 16.30% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-09-16.md to see failure details
Progress
-
client-proxy/test-https-proxy-request-invalid-char-in-url(6) -
wpt/test-streams(5) -
parallel/test-runner-run-watch(3) -
sequential/test-performance-eventloopdelay(3) -
async-hooks/test-emit-before-on-destroyed(2) -
parallel/test-debugger-heap-profiler(2) -
parallel/test-runner-watch-mode-kill-signal(2) -
Build timed out (after 30 minutes). Marking the build as failed.(8) -
Build timed out (after 60 minutes). Marking the build as failed.(7) -
Failed to create a temp file on /home/iojs/build/workspace/node(4) -
Backing channel 'JNLP4-connect connection from ... is disconnected.(3) -
Unexpected termination of the channel(3) -
fatal: No rebase in progress?(5) -
ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ...(2) -
Error: HEAD does not match expected COMMIT_SHA_CHECK'(2) -
fatal error: Killed signal terminated program cc1plus(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-09-16.md and the linked node-test-pull-request jobs to inspect the listed recurring failures. Work through the failing tests, timeouts, workspace errors, and connection failures; done means the reported CI failure patterns are resolved and the affected pull requests can pass reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100