Retry Cargo-Rail release downloads in CI - #435
Merged
Merged
Conversation
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.
Behaviour
.github/scripts/install_cargo_rail.pydownloads the pinned Cargo-Rail archive from GitHub's release CDN with a singleurlopen. Three desktop-check jobs failed today before running any Cargo step because that one request errored: a504 Gateway Time-outon PR #434 (run 34861096526) and an HTTP error on PR #432 (run 34858359289, Linux and Windows). The upstreamcargo-rail-actioninstaller already usescurl --retry 3for the same assets.The installer now retries the download up to four times with a short growing delay and a 60 s timeout per attempt, and still verifies the pinned SHA-256 after the download. Nothing else changes.
Checks
RUNNER_TEMP/GITHUB_PATHset: it downloads, verifies the checksum and installscargo-rail 0.25.0.