Repository navigation
agents: retry GitHub Actions jobs and handle setup-bazel network flakes - #4320
Merged
rickeylev merged 2 commits intoOct 23, 2026
Merged
Conversation
GitHub Actions jobs occasionally fail during `setup-bazel` with `Unable to find Bazelisk version` due to transient network errors. Previously, `buildkite-retry-job` only retried Buildkite jobs, and early matrix failures could not be rerun via `gh run rerun` until sibling jobs in the workflow run finished. Extend the CI monitoring, failure analysis, and retry skills to classify `setup-bazel` Bazelisk lookup failures as infrastructure flakes, fetch job logs via the GitHub API when runs are still in progress, and wait for parent GitHub Actions runs to complete before rerunning failed jobs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
GitHub Actions jobs occasionally fail during
setup-bazelwithUnable to find Bazelisk versiondue to transient network errors.Previously,
buildkite-retry-jobonly retried Buildkite jobs, andearly matrix failures could not be rerun via
gh run rerununtilsibling jobs in the workflow run finished.
Extend the CI monitoring, failure analysis, and retry skills to
classify
setup-bazelBazelisk lookup failures as infrastructureflakes, fetch job logs via the GitHub API when runs are still in
progress, and wait for parent GitHub Actions runs to complete before
rerunning failed jobs.