CI: retry CMake configure to survive transient Oboe FetchContent clone failures#259
Merged
winnerspiros merged 1 commit intomasterfrom Apr 23, 2026
Conversation
…lures Agent-Logs-Url: https://github.com/winnerspiros/osu/sessions/cbfdde86-494f-4e8b-8ac0-58ea639db24b Co-authored-by: winnerspiros <1675249+winnerspiros@users.noreply.github.com>
Copilot created this pull request from a session on behalf of
winnerspiros
April 23, 2026 16:10
View session
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.
Run 24845529416 failed during the native build because
FetchContenthit a transient GitHub outage while cloninggoogle/oboe:githas no built-in retry for HTTP 5xx, so a single flaky response from github.com aborts the whole release build.Changes
.github/workflows/release.yml— wrap thecmakeconfigure step (the one that triggers the OboeFetchContentclone) in a 5-attempt retry loop with incremental backoff (10s / 20s / 30s / 40s). Each retryrm -rfsbuild-native/$ABIfirst soFetchContentre-clones from a clean state rather than tripping on half-written stamp files.cmake --buildis unchanged and only runs after a successful configure.No CMake or source changes — the underlying Oboe pin (
main, shallow) is intentional and the failure mode is purely network flakiness on the runner.