CI Reliability 2026-08-03
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/75308 to node-test-pull-request/75406 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-08-03.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-08-03 00:28 | 1 | 8 | 30 | 3 | 58 | 8.33% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-08-03.md to see failure details
Progress
-
client-proxy/test-https-proxy-request-connection-refused(4) -
sequential/test-watch-mode-restart-esm-loading-error(4) -
client-proxy/test-https-proxy-request(3) -
- /home/iojs/build/workspace/node-test-linter/test/parallel/test-dtls-accessors.mjs(2) -
- /home/iojs/build/workspace/node-test-linter/test/parallel/test-dtls-alpn.mjs(2) -
- /home/iojs/build/workspace/node-test-linter/test/parallel/test-dtls-ciphers.mjs(2) -
- /home/iojs/build/workspace/node-test-linter/test/parallel/test-dtls-client-cert.mjs(2) -
- /home/iojs/build/workspace/node-test-linter/test/parallel/test-dtls-connect-error-cleanup.mjs(2) -
- /home/iojs/build/workspace/node-test-linter/test/parallel/test-dtls-destroy-in-callback.mjs(2) -
- /home/iojs/build/workspace/node-test-linter/test/parallel/test-dtls-errors.mjs(2) -
- /home/iojs/build/workspace/node-test-linter/test/parallel/test-dtls-keylog.mjs(2) -
- /home/iojs/build/workspace/node-test-linter/test/parallel/test-dtls-mtu.mjs(2) -
- /home/iojs/build/workspace/node-test-linter/test/parallel/test-dtls-options.mjs(2) -
- /home/iojs/build/workspace/node-test-linter/test/parallel/test-dtls-reject-unauthorized.mjs(2) -
- /home/iojs/build/workspace/node-test-linter/test/parallel/test-dtls-robustness.mjs(2) -
- /home/iojs/build/workspace/node-test-linter/test/parallel/test-dtls-send.mjs(2) -
- /home/iojs/build/workspace/node-test-linter/test/parallel/test-dtls-session-table-cleanup.mjs(2) -
- /home/iojs/build/workspace/node-test-linter/test/parallel/test-dtls-srtp.mjs(2) -
- /home/iojs/build/workspace/node-test-linter/test/parallel/test-dtls-unhandled-rejection.mjs(2) -
- /home/iojs/build/workspace/node-test-linter/test/parallel/test-dtls-verify-identity.mjs(2) -
es-module/test-vm-contextified-script-leak(2) -
parallel/test-http2-reset-happy-close(2) -
parallel/test-sqlite-backup(2) -
parallel/test-timers-immediate-queue(2) -
wpt/test-streams(2) -
Build timed out (after 30 minutes). Marking the build as failed.(2) -
Unexpected termination of the channel(2) -
sh: line 12: [: -gt: unary operator expected(7) -
Failed to trigger fanned build(6) -
fatal: No rebase in progress?(6) -
ERROR: out of memory(4) -
Failed to trigger node-test-commit(4) -
Error: Only one of 'ltcg', 'thin-lto', or 'lto' can be specified.(2) -
fatal error: too many errors emitted, stopping now [-ferror-limit=](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/2026-08-03.md and the linked node-test-pull-request builds, then reproduce the listed failures such as the client-proxy, watch-mode, DTLS, SQLite, and timer tests. Triage each named test or CI error to identify its cause and verify fixes against the affected jobs. Done means the recurring failures are resolved and the CI run is reliably green.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell, sqlite
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100