-
Notifications
You must be signed in to change notification settings - Fork 12.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Include extraction in the retrying for submodule download #106680
Include extraction in the retrying for submodule download #106680
Conversation
The code to download larger submodules previously used retries around the `curl` invocation to handle network failures, but we saw in recent build failures that failures can also happen during extraction, for example if a response got terminated early. This commit moves the retry outwards, wrapping the whole download+extraction function in the retrying code. This means, if the extraction fails the tarball will be re-downloaded.
r? @jyn514 (rustbot has picked a reviewer for you, use r? to override) |
@bors r+ p=51 |
🌲 The tree is currently closed for pull requests below priority 50. This pull request will be tested once the tree is reopened. |
⌛ Testing commit 48291f1 with merge b030ab677278e6cc1600e4cd54a87b55972e0a55... |
💔 Test failed - checks-actions |
@bors retry |
⌛ Testing commit 48291f1 with merge 7b96e10b46410dd20cb6f8a39754a59ef62aa3f4... |
The job Click to see the possible cause of the failure (guessed by this bot)
|
Stuck in queue? @bors r- |
IIRC bors commands on closed PRs don't work, I guess we have to synchronize the queue or reopen this to r- (it needs Pietro to restore the branch). |
I've initiated the synchronization |
@fee1-dead, when clicking the synchronize button, you need to go through the queue after it is finished and clean up things. Synchronize is fairly buggy. For example, if a PR was approved, but failed in CI, Synchronize will cause it to be re-approved. I think there are other issues like |
thanks for the information, and sorry about not following up.. it was my first time doing a synchronize and I did not know the risks. It is probably best to change the confirmation message such that people will understand exactly what would happen after pushing the button. |
The code to download larger submodules previously used retries around the
curl
invocation to handle network failures, but we saw in recent build failures that failures can also happen during extraction, for example if a response got terminated early.This commit moves the retry outwards, wrapping the whole download+extraction function in the retrying code. This means, if the extraction fails the tarball will be re-downloaded.