CI Reliability 2026-08-27

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

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

Progress

• error: could not apply 61890720c8a... add readme and initial code (7)
• ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error? (3)
• Failed to trigger node-test-commit (3)
• error: could not apply a7909014f77... tls: implement tls.getCACertificates() (3)
• fatal: No rebase in progress? (3)
• fatal: no rebase in progress (3)
• Error: HEAD does not match expected COMMIT_SHA_CHECK' (2)
• error: could not apply 7b6b21a8aae... doc: move histogram.burnRate to correct location in doc (2)
• node-api/test_sea_addon/test (17)
• sea/test-build-sea (17)
• sea/test-build-sea-executable-field (17)
• sea/test-single-executable-application (17)
• sea/test-single-executable-application-asset-keys (17)
• sea/test-single-executable-application-asset-keys-empty (17)
• sea/test-single-executable-application-assets (17)
• sea/test-single-executable-application-assets-raw (17)
• sea/test-single-executable-application-disable-experimental-sea-warning (17)
• sea/test-single-executable-application-empty (17)
• sea/test-single-executable-application-esm (17)
• sea/test-single-executable-application-esm-code-cache (17)
• sea/test-single-executable-application-exec-argv (17)
• sea/test-single-executable-application-exec-argv-empty (17)
• sea/test-single-executable-application-exec-argv-extension-cli (17)
• sea/test-single-executable-application-exec-argv-extension-env (17)
• sea/test-single-executable-application-exec-argv-extension-none (17)
• sea/test-single-executable-application-inspect (17)
• sea/test-single-executable-application-inspect-in-sea-flags (17)
• sea/test-single-executable-application-snapshot (17)
• sea/test-single-executable-application-snapshot-and-code-cache (17)
• sea/test-single-executable-application-snapshot-worker (17)
• sea/test-single-executable-application-use-code-cache (17)
• parallel/test-fastutf8stream-reopen (7)
• parallel/test-stream-pipeline-http2 (6)
• parallel/test-fs-watch-recursive-delete-race (5)
• parallel/test-inspect-async-hook-setup-at-inspect (5)
• sequential/test-fs-watch (5)
• parallel/test-fs-watch-recursive-delete (4)
• parallel/test-watch-mode-files_watcher (4)
• parallel/test-watch-mode-files_watcher-clear (4)
• sequential/test-debugger-pid (4)
• parallel/test-fastutf8stream-destroy (3)
• parallel/test-vfs-real-provider-watch (3)
• sequential/test-watch-mode-worker (3)
• parallel/test-fs-watch (2)
• parallel/test-permission-net-udp-handle (2)
• pummel/test-fs-watch-non-recursive (2)
• test-runner/test-run-watch-cwd-isolation-none (2)
• test-runner/test-run-watch-cwd-isolation-none-argv (2)

Start with reports/2026-08-27.md and the linked node-test-pull-request Jenkins runs to inspect the reported failures, especially the SEA, watch, and rebase-related jobs. Done means the recurring failures listed in the issue are resolved or explained and the affected CI runs return to a reliable green state.