CI Reliability 2026-05-28

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

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

Progress

• parallel/test-debugger-probe-failure-resume (9)
• parallel/test-fs-watch-recursive-delete (7)
• parallel/test-debugger-probe-timeout (6)
• async-hooks/test-improper-order (3)
• parallel/test-webcrypto-crypto-job-mode (3)
• ffi/test-ffi-void-parameter (2)
• parallel/test-fs-read-stream (2)
• parallel/test-http2-close-while-writing (2)
• sequential/test-debugger-pid (2)
• sequential/test-perf-hooks (2)
• wpt/test-hr-time (2)
• wpt/test-streams (2)
• Build timed out (after 60 minutes). Marking the build as failed. (2)
• Unexpected termination of the channel (2)
• ERROR: Error fetching remote repo 'origin' (2)
• fatal: No rebase in progress? (12)
• error: could not apply 61890720c8a... add readme and initial code (7)
• ERROR: out of memory (2)
• sh: line 1: 429:: command not found (2)

Read reports/2026-05-28.md and inspect the linked node-test-pull-request builds, starting with one unchecked test or infrastructure failure. Use the build output and the listed failure counts to establish what is reproducible; done means the selected reliability item is resolved and its progress entry can be checked.