CI Reliability 2025-09-12
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/69107 to node-test-pull-request/69195 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-09-12.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-09-12 00:10 | 4 | 21 | 21 | 2 | 52 | 22.34% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-09-12.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(5) -
Failed to create a temp file on /home/iojs/build/workspace/node(5) -
Build timed out (after 60 minutes). Marking the build as failed.(3) -
Backing channel 'JNLP4-connect connection from ... is disconnected.(2) -
fatal: No rebase in progress?(5) -
fatal error: Killed signal terminated program cc1plus(3) -
fatal error: ld terminated with signal 9 [Killed](2) -
client-proxy/test-https-proxy-request-invalid-char-in-url(6) -
parallel/test-without-async-context-frame(5) -
wpt/test-streams(5) -
parallel/test-runner-run-watch(4) -
async-hooks/test-emit-before-on-destroyed(3) -
sequential/test-performance-eventloopdelay(3) -
sequential/test-single-executable-application(3) -
sequential/test-single-executable-application-asset-keys(3) -
sequential/test-single-executable-application-asset-keys-empty(3) -
sequential/test-single-executable-application-assets(3) -
sequential/test-single-executable-application-assets-raw(3) -
sequential/test-single-executable-application-disable-experimental-sea-warning(3) -
sequential/test-single-executable-application-exec-argv(3) -
sequential/test-single-executable-application-exec-argv-empty(3) -
sequential/test-single-executable-application-exec-argv-extension-cli(3) -
sequential/test-single-executable-application-exec-argv-extension-env(3) -
sequential/test-single-executable-application-exec-argv-extension-none(3) -
sequential/test-single-executable-application-inspect(3) -
sequential/test-single-executable-application-inspect-in-sea-flags(3) -
sequential/test-single-executable-application-snapshot(3) -
sequential/test-single-executable-application-snapshot-and-code-cache(3) -
sequential/test-single-executable-application-snapshot-worker(3) -
sequential/test-single-executable-application-use-code-cache(3) -
parallel/test-runner-watch-mode-kill-signal(2) -
parallel/test-zlib-brotli-16GB(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-12.md and the linked node-test-pull-request builds from 69107 through 69195. Use the Progress list to investigate the repeated timeout, infrastructure, build, and test failures. Done means the identified failures are resolved and the affected CI 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
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100