-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Set values for Nuget.Client EXPERIMENTAL_HTTP_RETRY #58386
Set values for Nuget.Client EXPERIMENTAL_HTTP_RETRY #58386
Conversation
…d in newer Nuget.Client
I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label. |
Tagging subscribers to this area: @dotnet/runtime-infrastructure Issue DetailsChanges to try out experimental retry feature introduced in newer Nuget.Client. Environmental values enable longer delays, configurable number of retries, and special understanding of TCP hang-up. See NuGet/Home#11027 for details Pipelines that had retry-inducing issues with restore, but did not fail from the previous PR buildMono Product Build windows x86 debug <-- HTTP Client timeout
Build Browser wasm Release AllSubsets_Mono_WasmBuildTests <-- TCP Socket hangup
Libraries Build Linux x64 Debug <-- different kind of HTTP client timeout
CoreCLR Product Build windows arm checked <-- DNS failure
|
Changes to try out experimental retry feature introduced in newer Nuget.Client. Environmental values enable longer delays, configurable number of retries, and special understanding of TCP hang-up. See NuGet/Home#11027 for details
Pipelines that had retry-inducing issues with restore, but did not fail from the previous PR build
Mono Product Build windows x86 debug <-- HTTP Client timeout
Build Browser wasm Release AllSubsets_Mono_WasmBuildTests <-- TCP Socket hangup
Libraries Build Linux x64 Debug <-- different kind of HTTP client timeout
CoreCLR Product Build windows arm checked <-- DNS failure