CI Reliability 2026-05-29

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

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

Progress

• parallel/test-fs-watch-recursive-delete (6)
• async-hooks/test-improper-order (3)
• parallel/test-debugger-probe-failure-resume (3)
• sequential/test-perf-hooks (3)
• parallel/test-debugger-probe-timeout (2)
• parallel/test-fs-read-stream (2)
• parallel/test-http2-close-while-writing (2)
• parallel/test-webcrypto-crypto-job-mode (2)
• wpt/test-streams (2)
• Build timed out (after 60 minutes). Marking the build as failed. (2)
• Unexpected termination of the channel (2)
• Command "git reset --hard" returned status code 128: (2)
• fatal: No rebase in progress? (10)
• error: could not apply 61890720c8a... add readme and initial code (5)
• ERROR: out of memory (2)
• sh: line 1: 429:: command not found (2)

Start with reports/2026-05-29.md and the linked node-test-pull-request jobs to inspect the failure details behind the progress list. Review the named test failures and CI errors first; done means the listed recurring failures have been resolved and the affected pull requests can pass reliably.