Skip to content

CI Reliability 2026-06-10 #1567

@github-actions

Description

@github-actions

Failures in node-test-pull-request/73909 to node-test-pull-request/74008 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-06-10.md)

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2026-06-10 00:39 0 24 17 4 55 25.00%

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

Progress

  • sea/test-build-sea (4)
  • sea/test-build-sea-already-exists (4)
  • sea/test-build-sea-custom-argv0 (4)
  • sea/test-build-sea-executable-field (4)
  • sea/test-build-sea-missing-output (4)
  • sea/test-single-executable-application-asset-keys (4)
  • sea/test-single-executable-application-asset-keys-empty (4)
  • sea/test-single-executable-application-assets (4)
  • sea/test-single-executable-application-assets-raw (4)
  • sea/test-single-executable-application-exec-argv (4)
  • sea/test-single-executable-application-exec-argv-extension-env (4)
  • sea/test-single-executable-application-exec-argv-extension-none (4)
  • addons/worker-addon-exit/test (3)
  • sea/test-single-executable-application-disable-experimental-sea-warning (3)
  • sea/test-single-executable-application-empty (3)
  • sea/test-single-executable-application-esm (3)
  • sea/test-single-executable-application-esm-code-cache (3)
  • sea/test-single-executable-application-exec-argv-empty (3)
  • sea/test-single-executable-application-exec-argv-extension-cli (3)
  • sea/test-single-executable-application-snapshot-and-code-cache (3)
  • wpt/test-webcrypto (3)
  • parallel/test-debugger-probe-failure-process-exit (2)
  • parallel/test-http-server-consumed-timeout (2)
  • sea/test-single-executable-application-inspect (2)
  • sea/test-single-executable-application-snapshot (2)
  • sea/test-single-executable-application-snapshot-worker (2)
  • Build timed out (after 60 minutes). Marking the build as failed. (2)
  • ERROR: Error fetching remote repo 'origin' (6)
  • Failed to trigger fanned build (8)
  • ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (2)
  • Error: Only one of 'ltcg', 'thin-lto', or 'lto' can be specified. (2)
  • fatal: No rebase in progress? (2)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions