CI Reliability 2026-02-26

Failures in node-test-pull-request/71367 to node-test-pull-request/71453 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-02-26.md)

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

Progress

• Build timed out (after 60 minutes). Marking the build as failed. (2)
• ERROR: Error fetching remote repo 'origin' (4)
• fatal: No rebase in progress? (3)
• Error: 'utf-8' codec can't decode byte 0xc1 in position 243: invalid start byte (2)
• Failed to trigger sub builds (2)
• sequential/test-performance-eventloopdelay (4)
• async-hooks/test-emit-before-on-destroyed (3)
• parallel/test-async-context-frame (3)
• parallel/test-child-process-fork-exec-path (3)
• parallel/test-file-write-stream4 (3)
• parallel/test-http-client-response-domain (3)
• parallel/test-module-loading-globalpaths (3)
• parallel/test-promise-reject-callback-exception (3)
• parallel/test-runner-run-watch (3)
• parallel/test-tls-dhe (3)
• wpt/test-hr-time (3)
• async-hooks/test-improper-order (2)
• parallel/test-async-hooks-http-parser-destroy (2)
• parallel/test-runner-watch-mode (2)
• sea/test-build-sea (2)
• sea/test-build-sea-already-exists (2)
• sea/test-build-sea-custom-argv0 (2)
• sea/test-build-sea-executable-field (2)
• sea/test-build-sea-missing-output (2)
• sea/test-single-executable-application-asset-keys (2)
• sea/test-single-executable-application-asset-keys-empty (2)
• sea/test-single-executable-application-assets (2)
• sea/test-single-executable-application-assets-raw (2)
• sea/test-single-executable-application-disable-experimental-sea-warning (2)
• sea/test-single-executable-application-empty (2)
• sea/test-single-executable-application-esm (2)
• sea/test-single-executable-application-exec-argv (2)
• sea/test-single-executable-application-exec-argv-extension-cli (2)
• test-runner/test-run-watch-without-file (2)

Start with the linked node-test-pull-request builds and the generated reports/2026-02-26.md report to inspect the listed failures. Work through the CI errors and failing Node.js tests, using the Progress checklist to track completion; done means the identified failures are resolved and the affected builds become reliable.