Skip to content
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

Official build broken restoring internal tools #2199

Closed
jaredpar opened this issue Jan 25, 2020 · 1 comment · Fixed by #2255
Closed

Official build broken restoring internal tools #2199

jaredpar opened this issue Jan 25, 2020 · 1 comment · Fixed by #2255
Assignees
Labels
area-Infrastructure-coreclr untriaged New issue has not been triaged by the area owner

Comments

@jaredpar
Copy link
Member

The change to restore our internal tools appears to have broken the official builds. Post merge they are failing with the following error:

Build started 1/25/2020 4:09:22 PM.
     1>Project "F:\workspace\_work\1\s\eng\common\internal\Tools.csproj" on node 1 (Restore target(s)).
     1>Restore:
         Restoring packages for F:\workspace\_work\1\s\eng\common\internal\Tools.csproj...
     1>C:\Program Files\dotnet\sdk\3.0.100\NuGet.targets(123,5): error : Problem starting the plugin 'C:\Users\vsagent\.nuget\plugins\netcore\CredentialProvider.Microsoft\CredentialProvider.Microsoft.dll'. Plugin 'CredentialProvider.Microsoft' failed within 5.570 seconds with exit code -1. [F:\workspace\_work\1\s\eng\common\internal\Tools.csproj]
     1>C:\Program Files\dotnet\sdk\3.0.100\NuGet.targets(123,5): error : Unable to load the service index for source https://devdiv.pkgs.visualstudio.com/_packaging/dotnet-core-internal-tooling/nuget/v3/index.json. [F:\workspace\_work\1\s\eng\common\internal\Tools.csproj]
C:\Program Files\dotnet\sdk\3.0.100\NuGet.targets(123,5): error :   Response status code does not indicate success: 401 (Unauthorized). [F:\workspace\_work\1\s\eng\common\internal\Tools.csproj]
     1>Done Building Project "F:\workspace\_work\1\s\eng\common\internal\Tools.csproj" (Restore target(s)) -- FAILED.

PR that appears to have broken this #1846

Builds

@safern
Copy link
Member

safern commented Jan 29, 2020

I can confirm this is correctly fixed, we haven't hit this since my last fix went in.

@ghost ghost locked as resolved and limited conversation to collaborators Dec 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-Infrastructure-coreclr untriaged New issue has not been triaged by the area owner
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants