Closed jaredpar closed 4 years ago
I couldn't add an area label to this Issue.
Checkout this page to find out which area owner to ping, or please add exactly one area label to help train me in the future.
cc: @ViktorHofer
Try override DOTNET_CLI_HOME
to a temp location everytime.
could mitigate it for now
A mitigation is already in process: https://github.com/dotnet/runtime/pull/33871. Let's discuss the right fix in the sdk issue.
@ViktorHofer, @wli3, @safern I keep hitting this issue locally on my Linux box with Ubuntu 16.04. Latest master cleaned with git clean -xdf
. DOTNET_CLI_HOME workaround works, but is someone working on a real fix?
@janvorli
Have you tried nuking your NuGet package cache? Essentially run the following:
dotnet nuget locals all --clear
It's possible an old package is cached that is impacting this restore. If that doesn't fix it though we should probably open a new issue to track this as it's unlikely to be related to this specific instance.
@jaredpar that didn't help, the issue persists.
@janvorli can you open a new issue with the error that you're seeing locally? The error in this issue is specific to our official build so my assumption would be that there is a subtle difference here in what you're seeing.
Also could you attach / share out the binary log for restore (add -binaryLog
to the build.cmd/sh
invocation). That should help narrow down what is going on.
Looks like all our official builds are failing with the following restore exception: