Skip to content

CI Reliability 2026-07-26 #1612

Description

@github-actions

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2026-07-26 00:28 10 16 6 4 64 18.60%

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

Progress

  • parallel/test-repl-user-error-handler (19)
  • client-proxy/test-https-proxy-request-invalid-char-in-url (3)
  • parallel/test-debugger-probe-failure-process-exit (3)
  • parallel/test-runner-run-watch (3)
  • parallel/test-runner-watch-mode (3)
  • parallel/test-vfs-readdir-symlink-recursive (3)
  • sequential/test-performance-eventloopdelay (3)
  • sea/test-single-executable-application-disable-experimental-sea-warning (2)
  • test-runner/test-run-watch-emit-restarted (2)
  • ERROR: Error fetching remote repo 'origin' (5)
  • Command "git fetch --no-tags --force --progress -- git@github.com:nodejs/node.git +refs/heads/*:refs/remotes/origin/* +refs/pull/64399/head:refs/remotes/origin/_jenkins_local_branch" returned status code 128: (2)
  • fatal: No rebase in progress? (16)
  • error: could not apply 61890720c8a... add readme and initial code (14)
  • Failed to trigger fanned build (9)
  • ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error? (2)
  • sh: line 12: [: -gt: unary operator expected (2)

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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