Bump up download file timeout #39005
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
ghost
added
the
area-infrastructure
dougbu
approved these changes
Dec 13, 2021
Contributor
Author
|
/backport to release/6.0 |
Contributor
|
Started backporting to release/6.0: https://github.com/dotnet/aspnetcore/actions/runs/1580522418 |
Contributor
Author
|
/backport to release/5.0 |
Contributor
Author
|
/backport to release/3.1 |
Contributor
|
Started backporting to release/5.0: https://github.com/dotnet/aspnetcore/actions/runs/1580523692 |
Contributor
Author
|
/backport to release/2.1 |
11 tasks
Contributor
|
Started backporting to release/3.1: https://github.com/dotnet/aspnetcore/actions/runs/1580524289 |
Contributor
|
Started backporting to release/2.1: https://github.com/dotnet/aspnetcore/actions/runs/1580524544 |
11 tasks
Contributor
|
@TanayParikh backporting to release/3.1 failed, the patch most likely resulted in conflicts: $ git am --3way --ignore-whitespace --keep-non-patch changes.patch
Applying: Bump up download file timeout
Using index info to reconstruct a base tree...
M eng/tools/RepoTasks/DownloadFile.cs
Falling back to patching base and 3-way merge...
Auto-merging eng/tools/RepoTasks/DownloadFile.cs
CONFLICT (content): Merge conflict in eng/tools/RepoTasks/DownloadFile.cs
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Bump up download file timeout
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
Error: The process '/usr/bin/git' failed with exit code 128Please backport manually! |
Contributor
|
@TanayParikh backporting to release/2.1 failed, the patch most likely resulted in conflicts: $ git am --3way --ignore-whitespace --keep-non-patch changes.patch
Applying: Bump up download file timeout
Using index info to reconstruct a base tree...
A eng/tools/RepoTasks/DownloadFile.cs
Falling back to patching base and 3-way merge...
CONFLICT (modify/delete): eng/tools/RepoTasks/DownloadFile.cs deleted in HEAD and modified in Bump up download file timeout. Version Bump up download file timeout of eng/tools/RepoTasks/DownloadFile.cs left in tree.
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Bump up download file timeout
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
Error: The process '/usr/bin/git' failed with exit code 128Please backport manually! |
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.
MacOS jobs have had a significant increase in failure rates due to timing out when attempting to retrieve from blob storage. This PR increases the timeout value.
Example Pipeline: https://dev.azure.com/dnceng/public/_build/results?buildId=1507432&view=logs&jobId=9895f7d8-b062-540b-461c-07f8695bfcc6&j=9895f7d8-b062-540b-461c-07f8695bfcc6&t=a6c33838-4cf4-594d-88cb-801ae7f8db2f
I contacted first responders, there doesn't seem to be a known network/blob storage issue which would cause this.