Conversation
I'm pretty fed up with GitHub's reliability. Sometimes a clone just fails, their uptime has been spotty lately. Using our dependency auto-build feature for more packages, more frequently in CI, the opportunities for spurious failures have grown enough that it seems like every CI workflow (with 29 job variants these days) has a good chance of at least one job variant failing. That's a lot of noise in what's supposed to be a reliable signal about whether the PR passes or fails the testsuite on its own merits. So here is me being a little desperte -- I'm adding a CMake function execute_process_with_retry, that we use with the git clone of dependencies to try up to 5 times before a full failure. After the first failure, it waits 15 seconds. The delay doubles with each failure. If all attempts fail, it's a full job failure. Hopefully, any spurious GitHub clone unavailability that lasts less than a few minutes will just be glossed over and let us complete CI, at the cost of perhaps a minute or two delay, which seems like a small price to pay. Assisted by: Claude Code / claude-opus-5 Signed-off-by: Larry Gritz <lg@larrygritz.com>
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
1 participant
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.
I'm pretty fed up with GitHub's reliability. Sometimes a clone just fails, their uptime has been spotty lately. Using our dependency auto-build feature for more packages, more frequently in CI, the opportunities for spurious failures have grown enough that it seems like every CI workflow (with 29 job variants these days) has a good chance of at least one job variant failing. That's a lot of noise in what's supposed to be a reliable signal about whether the PR passes or fails the testsuite on its own merits. I'm constantly poking "rerun failed jobs" on people's PRs for no good reason, and having trouble separating which are temporary GitHub failures from which PRs are actually broken.
So here is me being a little desperate -- I'm adding a CMake function execute_process_with_retry, that we use with the git clone of dependencies to try up to 5 times before a full failure. After the first failure, it waits 15 seconds. The delay doubles with each failure. If all attempts fail, it's a full job failure. Hopefully, any spurious GitHub clone unavailability that lasts less than a few minutes will just be glossed over and let us complete CI, at the cost of perhaps a minute or two delay, which seems like a small price to pay.
Assisted by: Claude Code / claude-opus-5