CI Reliability 2025-05-03

Failures in node-test-pull-request/66456 to node-test-pull-request/66552 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-05-03.md)

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

Progress

• pummel/test-heapdump-shadow-realm (4)
• sequential/test-performance-eventloopdelay (4)
• sequential/test-tls-session-timeout (4)
• pummel/test-heapdump-http2 (3)
• pummel/test-heapdump-worker (3)
• parallel/test-buffer-tostring-rangeerror (2)
• parallel/test-debugger-break (2)
• parallel/test-http-get-pipeline-problem (2)
• parallel/test-runner-run-watch (2)
• parallel/test-stream-readable-unpipe-resume (2)
• parallel/test-whatwg-url-canparse (2)
• parallel/test-without-async-context-frame (2)
• parallel/test-zlib-brotli-16GB (2)
• pummel/test-process-hrtime (2)
• pummel/test-timers (2)
• Build timed out (after 30 minutes). Marking the build as failed. (7)
• Build timed out (after 60 minutes). Marking the build as failed. (3)
• fatal: No rebase in progress? (3)
• ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ... (2)
• fatal error: Killed signal terminated program cc1plus (2)

Start with reports/2025-05-03.md in the linked nodejs/reliability repository and inspect the Jenkins runs referenced in this issue. Use the listed test names and failure messages to investigate the CI failures; done means the applicable progress items are resolved and the CI is reliable again.