CI Reliability 2026-02-10

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

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

Progress

• parallel/test-http2-close-while-writing (4)
• sequential/test-single-executable-application-empty (3)
• test-runner/test-run-watch-without-file (3)
• async-hooks/test-emit-before-on-destroyed (2)
• parallel/test-child-process-fork-exec-path (2)
• parallel/test-esm-loader-hooks-inspect-wait (2)
• parallel/test-file-write-stream4 (2)
• parallel/test-http-client-response-domain (2)
• parallel/test-module-loading-globalpaths (2)
• parallel/test-promise-reject-callback-exception (2)
• parallel/test-repl-programmatic-history (2)
• parallel/test-runner-output (2)
• parallel/test-runner-watch-mode (2)
• parallel/test-zlib-brotli-16GB (2)
• sequential/test-performance-eventloopdelay (2)
• sequential/test-watch-mode-restart-esm-loading-error (2)
• wpt/test-hr-time (2)
• Failed to create a temp file on /home/iojs/build/workspace/node (4)
• Failed to trigger sub builds (3)
• ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error? (2)
• fatal: No rebase in progress? (2)
• Unexpected token '<', " (6)

Start with the linked reliability report for 2026-02-10 and inspect the listed node-test-pull-request failures. Compare the affected test names and CI errors, including temporary-file and sub-build failures, with their referenced job runs. Done means the identified failures are addressed and the corresponding CI checks no longer reproduce them.