CI Reliability 2026-02-28

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

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

Progress

• Failed to trigger node-test-commit (4)
• Error: 'utf-8' codec can't decode byte 0xc1 in position 243: invalid start byte (2)
• Failed to trigger sub builds (2)
• fatal: No rebase in progress? (2)
• parallel/test-debugger-heap-profiler (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-fs-write-stream-eagain (3)
• parallel/test-http-client-response-domain (3)
• parallel/test-module-loading-globalpaths (3)
• parallel/test-promise-reject-callback-exception (3)
• parallel/test-tls-dhe (3)
• async-hooks/test-improper-order (2)
• es-module/test-vm-contextified-script-leak (2)
• parallel/test-async-hooks-http-parser-destroy (2)
• parallel/test-runner-run-watch (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)
• sequential/test-performance-eventloopdelay (2)
• wpt/test-hr-time (2)

Start with reports/2026-02-28.md and the linked node-test-pull-request jobs to review the failure details. Use the listed CI errors and repeated test names as entry points, then run the affected jobs or tests. Done means the tracked failures are resolved and the Progress items can be checked off.