ci: retry the modflow executable download - #117
Merged
jdhughes-dev merged 1 commit intoSep 6, 2026
Conversation
The executables are fetched from github at the start of every test job. One job of thirty failed on develop when that connection was reset, before any test ran. The download is attempted twice before the job fails. The step in the release workflow is already conditional, so its retry combines that condition with the outcome of the first attempt rather than carrying a second if key.
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.
The executables are fetched from github at the start of every test job. One job of thirty failed on
developwhen that connection was reset withURLError: [Errno 104] Connection reset by peer, before any test ran. The download is attempted twice before the job fails.Passing
github_tokenwould not have helped: the action already falls back togithub.tokenwhen none is given, so the request was authenticated.The step in the release workflow is already conditional, so its retry combines that condition with the outcome of the first attempt.