CI Reliability 2026-03-16

Failures in node-test-pull-request/71688 to node-test-pull-request/71779 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-03-16.md)

Open https://github.com/nodejs/reliability/blob/main/reports/2026-03-16.md to see failure details

Progress

• parallel/test-npm-install (8)
• parallel/test-debugger-heap-profiler (5)
• sea/test-single-executable-application-assets (5)
• sea/test-single-executable-application-exec-argv-extension-cli (5)
• sea/test-single-executable-application-inspect-in-sea-flags (5)
• parallel/test-net-autoselectfamily (4)
• parallel/test-blob (3)
• parallel/test-http2-goaway-delayed-request (3)
• parallel/test-https-strict (3)
• parallel/test-inspector-network-http (3)
• parallel/test-zlib-brotli-16GB (3)
• sequential/test-performance-eventloopdelay (3)
• sequential/test-watch-mode-restart-esm-loading-error (3)
• test-runner/test-run-watch-run-duration (3)
• test-runner/test-run-watch-without-file (3)
• client-proxy/test-http-proxy-fetch (2)
• client-proxy/test-http-proxy-request-connection-refused (2)
• client-proxy/test-http-proxy-request-no-proxy-domain (2)
• client-proxy/test-https-proxy-fetch (2)
• client-proxy/test-https-proxy-request-connection-refused (2)
• client-proxy/test-use-env-proxy-cli-https (2)
• es-module/test-vm-contextified-script-leak (2)
• parallel/test-child-process-fork-closed-channel-segfault (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-esm-loader-hooks-inspect-wait (2)
• parallel/test-http-eof-on-connect (2)
• parallel/test-http-server-headers-timeout-pipelining (2)
• parallel/test-http-write-head-after-set-header (2)
• parallel/test-http2-compat-errors (2)
• parallel/test-http2-compat-serverresponse-statuscode (2)
• parallel/test-http2-many-writes-and-destroy (2)
• parallel/test-http2-max-settings (2)
• parallel/test-http2-misbehaving-flow-control (2)
• parallel/test-http2-misbehaving-flow-control-paused (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-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-agent-additional-options (2)
• parallel/test-https-keep-alive-drop-requests (2)
• parallel/test-inspector-exit-worker-in-wait-for-connection (2)
• parallel/test-net-connect-buffer2 (2)
• parallel/test-net-dns-lookup (2)
• parallel/test-net-listen-ipv6only (2)
• parallel/test-net-server-close (2)
• parallel/test-net-socket-destroy-twice (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)
• sequential/test-tls-session-timeout (2)
• test-runner/test-output-test-runner-watch-spec (2)
• test-runner/test-run-watch-repeatedly (2)
• Error: - process terminated with status 1, expected 0 (6)
• Failed to trigger node-test-commit (3)
• fatal: No rebase in progress? (3)

Start with reports/2026-03-16.md and the linked node-test-pull-request jobs to inspect the failure details. Review the listed failing tests, such as parallel/test-npm-install and sea/test-single-executable-application-assets, and identify which failures are actionable. Done means the reported CI failures have been addressed and the affected tests no longer fail repeatedly.