CI Reliability 2026-08-04
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/75347 to node-test-pull-request/75446 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-08-04.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-08-04 00:27 | 0 | 15 | 32 | 7 | 46 | 16.13% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-08-04.md to see failure details
Progress
-
parallel/test-sqlite-backup(5) -
sequential/test-watch-mode-restart-esm-loading-error(5) -
client-proxy/test-https-proxy-request-connection-refused(4) -
client-proxy/test-https-proxy-request(3) -
wpt/test-streams(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) -
test-runner/test-run-watch-emit-restarted(2) -
Unexpected termination of the channel(2) -
Command "git reset --hard" returned status code 128:(2) -
fatal: No rebase in progress?(6) -
Failed to trigger node-test-commit(5) -
ERROR: out of memory(3) -
sh: line 12: [: -gt: unary operator expected(3) -
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?(2) -
fatal: failed to run prune(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-04.md and the CI job range linked in the issue, then inspect the listed failures, especially the named test cases and infrastructure errors. Use the generated ncu-ci walk pr --stats=true --markdown report to compare failures. Done means the tracked recurring CI failures are resolved or otherwise accounted for and the progress list is updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100