CI Reliability 2026-03-13

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

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

Progress

• fatal: No rebase in progress? (4)
• Failed to trigger node-test-commit (2)
• parallel/test-debugger-heap-profiler (8)
• sequential/test-performance-eventloopdelay (4)
• es-module/test-vm-contextified-script-leak (3)
• parallel/test-http2-goaway-delayed-request (3)
• parallel/test-https-agent-additional-options (3)
• parallel/test-https-strict (3)
• parallel/test-inspector-exit-worker-in-wait-for-connection (3)
• parallel/test-net-autoselectfamily (3)
• parallel/test-tls-use-after-free-regression (3)
• client-proxy/test-http-proxy-fetch (2)
• client-proxy/test-http-set-global-proxy-from-env-fetch-empty (2)
• client-proxy/test-http-set-global-proxy-from-env-override-http (2)
• client-proxy/test-https-request-proxy-post (2)
• client-proxy/test-use-env-proxy-cli-https (2)
• parallel/test-blob (2)
• parallel/test-cluster-primary-kill (2)
• parallel/test-diagnostics-channel-http2-client-stream-body-no-chunks (2)
• parallel/test-diagnostics-channel-http2-client-stream-start (2)
• parallel/test-diagnostics-channel-http2-server-stream-close (2)
• parallel/test-heapsnapshot-near-heap-limit-worker (2)
• parallel/test-http-chunked-smuggling (2)
• parallel/test-http-eof-on-connect (2)
• parallel/test-http-pipeline-assertionerror-finish (2)
• parallel/test-http2-compat-serverrequest-end (2)
• parallel/test-http2-compat-serverresponse-createpushresponse (2)
• parallel/test-http2-compat-serverresponse-writehead (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-request-remove-connect-listener (2)
• parallel/test-http2-respond-file (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-settings-unsolicited-ack (2)
• parallel/test-https-client-renegotiation-limit (2)
• parallel/test-https-keep-alive-drop-requests (2)
• parallel/test-inspector-not-blocked-on-idle (2)
• parallel/test-net-after-close (2)
• parallel/test-net-bytes-read (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-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-snapshot-reproducible (2)
• parallel/test-tls-client-auth (2)
• parallel/test-tls-connect-memleak (2)
• parallel/test-tls-ticket-cluster (2)
• sequential/test-net-reconnect-error (2)
• sequential/test-tls-session-timeout (2)
• sequential/test-watch-mode-restart-esm-loading-error (2)
• test-runner/test-run-watch-run-duration (2)

Start with the generated report at reports/2026-03-13.md and the linked node-test-pull-request jobs, then inspect the listed failure names and the ncu-ci walk command output. Done means the causes of the recurring failures are addressed and the corresponding Progress checklist entries can be marked complete.