CI Reliability 2026-09-01

Failures in node-test-pull-request/76689 to node-test-pull-request/76788 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-09-01.md)

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

Progress

• Build timed out (after 60 minutes). Marking the build as failed. (2)
• ERROR: Error fetching remote repo 'origin' (3)
• ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error? (3)
• Error: 'utf-8' codec can't decode byte 0x88 in position 255: invalid start byte (2)
• Failed to trigger fanned build (2)
• Failed to trigger node-test-commit (2)
• parallel/test-fs-watch-recursive-delete-race (5)
• parallel/test-runner-run-watch (5)
• parallel/test-sqlite-backup (5)
• parallel/test-fs-watch-enoent (3)
• parallel/test-module-builtin-experimental (3)
• sequential/test-debugger-pid (3)
• parallel/test-external-memory-reasonable-size (2)
• parallel/test-http2-bidirectional-write-deadlock (2)
• parallel/test-inspect-async-hook-setup-at-inspect (2)

Start with reports/2026-09-01.md and the linked node-test-pull-request builds, using the listed failure messages to identify which failures are actionable. Review the affected tests, including parallel/test-fs-watch-recursive-delete-race and parallel/test-runner-run-watch, and determine whether each failure is infrastructure or a test defect. Done means the relevant CI failures are diagnosed and the build is reliably green.