CI Reliability 2024-09-05

Failures in node-test-pull-request/61855 to node-test-pull-request/61950 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2024-09-05.md)

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

Progress

• Failed to create a temp file on /Users/iojs/build/workspace/node-test-commit-osx/nodes/osx11-x64 (13)
• Backing channel 'JNLP4-connect connection from ... is disconnected. (2)
• Build timed out (after 60 minutes). Marking the build as failed. (2)
• Command "git clean -fdx" returned status code 143: (3)
• fatal: No rebase in progress? (19)
• Error: - process terminated with status 1, expected 0 (8)
• Error: EBUSY: resource busy or locked, rmdir '\\?\C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.637' (3)
• parallel/test-async-context-frame (14)
• pummel/test-fs-readfile-tostring-fail (11)
• parallel/test-runner-run-watch (9)
• sequential/test-http-server-request-timeouts-mixed (7)
• parallel/test-esm-loader-hooks-inspect-wait (6)
• parallel/test-http2-socket-close (4)
• parallel/test-runner-watch-mode-complex (4)
• parallel/test-dns (3)
• parallel/test-sqlite-statement-sync (3)
• async-hooks/test-writewrap (2)
• parallel/test-inspector-strip-types (2)
• parallel/test-macos-app-sandbox (2)
• parallel/test-worker-nearheaplimit-deadlock (2)

Start with reports/2024-09-05.md and the linked node-test-pull-request jobs, then use the listed failure categories and test names to separate infrastructure failures from test failures. Review the output from ncu-ci walk pr --stats=true --markdown reports/2024-09-05.md; done means the repeated failures are addressed and subsequent CI runs no longer reproduce them.