CI Reliability 2025-09-15
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/69136 to node-test-pull-request/69216 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-09-15.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-09-15 00:11 | 11 | 16 | 19 | 7 | 47 | 19.51% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-09-15.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(4) -
async-hooks/test-emit-before-on-destroyed(2) -
parallel/test-without-async-context-frame(2) -
sequential/test-performance-eventloopdelay(2) -
Build timed out (after 30 minutes). Marking the build as failed.(6) -
Failed to create a temp file on /home/iojs/build/workspace/node(4) -
Backing channel 'JNLP4-connect connection from ... is disconnected.(3) -
Build timed out (after 60 minutes). Marking the build as failed.(3) -
Unexpected termination of the channel(2) -
fatal: No rebase in progress?(3) -
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-15.md and the linked node-test-pull-request builds, using the listed failure names to identify which failures are reproducible. The generated command is ncu-ci walk pr --stats=true --markdown; done means addressing the listed CI failures and confirming the affected jobs no longer fail repeatedly.
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