Repository navigation
Try a download again when it comes back empty - #255
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
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.
Part of #244. The rucc job of a 7.4-rc2 defconfig census (43827743821) failed twice in a row because
linux-7.4-rc2.tar.gzcame back from git.kernel.org as an empty file. curl saw status 200, so the download passed and the hash check then failed with the SHA-256 of nothing. The gcc-16 job of the same run asked for the same snapshot at the same moment and got the whole file, which fits cgit answering with an empty body while it is still making the snapshot.downloadnow tries again when the file it got is empty, up to four times, waiting 30, 60 and then 90 seconds between tries. A real HTTP error still fails at once as before. The GitHub mirror does not help here, since its tarball is packed differently and never matches the pinned hash.Checked with
cargo fmt --check,cargo clippy -p rk --all-targets -D warningsand the rk tests.