CI Reliability 2026-03-14
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/71659 to node-test-pull-request/71751 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-03-14.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-03-14 00:15 | 9 | 16 | 4 | 11 | 60 | 20.00% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-03-14.md to see failure details
Progress
-
parallel/test-debugger-heap-profiler(8) -
sequential/test-performance-eventloopdelay(5) -
parallel/test-net-autoselectfamily(4) -
parallel/test-npm-install(4) -
es-module/test-vm-contextified-script-leak(3) -
parallel/test-blob(3) -
parallel/test-http2-goaway-delayed-request(3) -
parallel/test-https-agent-additional-options(3) -
parallel/test-https-strict(3) -
parallel/test-zlib-brotli-16GB(3) -
sequential/test-watch-mode-restart-esm-loading-error(3) -
test-runner/test-run-watch-run-duration(3) -
client-proxy/test-http-proxy-fetch(2) -
client-proxy/test-http-set-global-proxy-from-env-fetch-empty(2) -
client-proxy/test-https-proxy-fetch(2) -
client-proxy/test-use-env-proxy-cli-https(2) -
parallel/test-cluster-primary-kill(2) -
parallel/test-diagnostics-channel-http2-client-stream-body-multiple-buffers(2) -
parallel/test-diagnostics-channel-http2-client-stream-body-no-chunks(2) -
parallel/test-diagnostics-channel-http2-client-stream-body-single-string(2) -
parallel/test-diagnostics-channel-http2-client-stream-start(2) -
parallel/test-diagnostics-channel-http2-server-stream-close(2) -
parallel/test-http-eof-on-connect(2) -
parallel/test-http-pipeline-assertionerror-finish(2) -
parallel/test-http-server-headers-timeout-pipelining(2) -
parallel/test-http2-compat-errors(2) -
parallel/test-http2-compat-serverrequest-end(2) -
parallel/test-http2-compat-write-head-destroyed(2) -
parallel/test-http2-max-settings(2) -
parallel/test-http2-misbehaving-flow-control(2) -
parallel/test-http2-raw-headers-defaults(2) -
parallel/test-http2-respond-file(2) -
parallel/test-http2-respond-file-push(2) -
parallel/test-http2-respond-file-range(2) -
parallel/test-http2-respond-no-data(2) -
parallel/test-http2-server-push-disabled(2) -
parallel/test-http2-server-sessionerror(2) -
parallel/test-http2-server-stream-session-destroy(2) -
parallel/test-http2-settings-unsolicited-ack(2) -
parallel/test-https-keep-alive-drop-requests(2) -
parallel/test-inspector-exit-worker-in-wait-for-connection(2) -
parallel/test-net-after-close(2) -
parallel/test-net-bytes-stats(2) -
parallel/test-net-connect-buffer2(2) -
parallel/test-net-connect-reset-until-connected(2) -
parallel/test-net-dns-lookup(2) -
parallel/test-net-listen-ipv6only(2) -
parallel/test-net-server-close(2) -
parallel/test-net-server-max-connections(2) -
parallel/test-net-socket-destroy-twice(2) -
parallel/test-net-stream(2) -
parallel/test-net-write-connect-write(2) -
parallel/test-node-output-eval(2) -
parallel/test-permission-fs-read(2) -
parallel/test-tls-client-auth(2) -
parallel/test-tls-connect-memleak(2) -
parallel/test-tls-ticket-cluster(2) -
parallel/test-tls-use-after-free-regression(2) -
sea/test-single-executable-application-assets(2) -
sea/test-single-executable-application-exec-argv-extension-cli(2) -
sea/test-single-executable-application-inspect-in-sea-flags(2) -
sequential/test-tls-session-timeout(2) -
test-runner/test-run-watch-without-file(2) -
fatal: No rebase in progress?(4) -
Failed to trigger node-test-commit(3)
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-03-14.md and the linked node-test-pull-request runs, then review the unchecked failures listed in this issue. Use the named test paths and the ncu-ci walk command as entry points for investigation. Done means addressing the reported reliability failures and marking the corresponding progress items complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100