dotnet workload restore
runtime jumps from 25 seconds to 4 minutes when nuget feed is AzDO instead of nuget.org
#43870
Labels
Area-Workloads
needs team triage
Requires a full team discussion
untriaged
Request triage from a team member
Describe the bug
Frequent pipeline failures due to nuget.org not responding to package restore requests drives me to consider using a private Azure Artifacts feed instead of nuget.org in nuget.config.
But this change has an unexpected side-effect: the time to run
dotnet workload restore
jumps extremely:The macOS agent is the only one to display the following errors, which it does only after the change:
Eventually the work completes (successfully I guess, because the rest of the build succeeds.)
This is repeatable. And the macOS agent has the authentication necessary to pull from the private feed.
Further technical details
The text was updated successfully, but these errors were encountered: