CI Reliability 2026-05-27

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

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

Progress

• parallel/test-debugger-probe-failure-resume (17)
• parallel/test-debugger-probe-timeout (8)
• parallel/test-webcrypto-crypto-job-mode (6)
• parallel/test-fs-watch-recursive-delete (5)
• sequential/test-debugger-pid (3)
• async-hooks/test-improper-order (2)
• ffi/test-ffi-void-parameter (2)
• parallel/test-fs-read-stream (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? (13)
• error: could not apply 61890720c8a... add readme and initial code (9)
• ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ... (2)
• ERROR: out of memory (2)

Open reports/2026-05-27.md, generated with ncu-ci walk pr --stats=true --markdown reports/2026-05-27.md, and review the failure details behind the listed CI jobs. Start with one recurring test or infrastructure failure, such as parallel/test-debugger-probe-failure-resume or the Git rebase errors, and trace its failing job. Done means the identified failures no longer recur and the affected CI runs are green.