Skip to content

CI Reliability 2026-07-29 #1615

Description

@github-actions

Failures in node-test-pull-request/75176 to node-test-pull-request/75271 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-07-29.md)

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2026-07-29 00:23 1 12 15 6 66 12.90%

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

Progress

  • parallel/test-vfs-readdir-symlink-recursive (3)
  • test-runner/test-run-watch-cwd-isolation-none-argv (3)
  • parallel/test-crypto-x509 (2)
  • parallel/test-http2-reset-happy-close (2)
  • sea/test-build-sea (2)
  • sea/test-build-sea-already-exists (2)
  • sea/test-build-sea-custom-argv0 (2)
  • sea/test-build-sea-executable-field (2)
  • sea/test-build-sea-missing-output (2)
  • sea/test-single-executable-application-asset-keys (2)
  • sea/test-single-executable-application-asset-keys-empty (2)
  • sea/test-single-executable-application-assets (2)
  • sea/test-single-executable-application-assets-raw (2)
  • sea/test-single-executable-application-disable-experimental-sea-warning (2)
  • sea/test-single-executable-application-empty (2)
  • sea/test-single-executable-application-esm (2)
  • sea/test-single-executable-application-esm-code-cache (2)
  • sea/test-single-executable-application-exec-argv (2)
  • sea/test-single-executable-application-exec-argv-empty (2)
  • sea/test-single-executable-application-exec-argv-extension-cli (2)
  • sea/test-single-executable-application-exec-argv-extension-env (2)
  • ERROR: Error fetching remote repo 'origin' (3)
  • Failed to trigger fanned build (25)
  • sh: line 12: [: -gt: unary operator expected (6)
  • fatal: No rebase in progress? (5)
  • Error: Only one of 'ltcg', 'thin-lto', or 'lto' can be specified. (4)
  • error: could not apply 4f844f4380a... repl: use inspector over vm (4)
  • error: could not apply 61890720c8a... add readme and initial code (4)
  • Failed to trigger node-test-commit (3)
  • ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error? (2)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions