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

CI builds failing with restore error #33837

Closed
jaredpar opened this issue Mar 20, 2020 · 9 comments · Fixed by #33871
Closed

CI builds failing with restore error #33837

jaredpar opened this issue Mar 20, 2020 · 9 comments · Fixed by #33871
Assignees
Labels
area-Infrastructure blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' blocking-official-build untriaged New issue has not been triaged by the area owner

Comments

@jaredpar
Copy link
Member

Looks like all our official builds are failing with the following restore exception:

installer.tasks -> F:\workspace\_work\1\s\artifacts\bin\installer.tasks\Debug\net46\installer.tasks.dll
installer.tasks -> F:\workspace\_work\1\s\artifacts\bin\installer.tasks\Debug\netstandard2.0\installer.tasks.dll
Determining projects to restore...
Microsoft.DotNet.ToolPackage.ResolverCacheInconsistentException: more than one row for coverlet.console-1.7.0-net5.0-any-coverlet
   at Microsoft.DotNet.ToolPackage.LocalToolsResolverCache.TryGetMatchingRestoredCommand(RestoredCommandIdentifier restoredCommandIdentifier, CacheRow[] cacheTable, RestoredCommand& restoredCommandList)
   at Microsoft.DotNet.ToolPackage.LocalToolsResolverCache.TryLoad(RestoredCommandIdentifier restoredCommandIdentifier, RestoredCommand& restoredCommand)
   at Microsoft.DotNet.Tools.Tool.Restore.ToolRestoreCommand.PackageHasBeenRestored(ToolManifestPackage package, String targetFramework)
   at Microsoft.DotNet.Tools.Tool.Restore.ToolRestoreCommand.InstallPackages(ToolManifestPackage package, Nullable`1 configFile)
   at Microsoft.DotNet.Tools.Tool.Restore.ToolRestoreCommand.<>c__DisplayClass11_0.<Execute>b__0(ToolManifestPackage package)
   at System.Linq.Enumerable.SelectArrayIterator`2.MoveNext()
   at System.Linq.ParallelEnumerable.ToList[TSource](ParallelQuery`1 source)
   at System.Linq.ParallelEnumerable.ToArray[TSource](ParallelQuery`1 source)
   at Microsoft.DotNet.Tools.Tool.Restore.ToolRestoreCommand.Execute()
   at Microsoft.DotNet.Cli.DotNetTopLevelCommandBase.RunCommand(String[] args)
   at Microsoft.DotNet.Tools.Tool.ToolCommand.Run(String[] args)
   at Microsoft.DotNet.Cli.Program.ProcessArgs(String[] args, ITelemetry telemetryClient)
   at Microsoft.DotNet.Cli.Program.Main(String[] args)
@Dotnet-GitSync-Bot
Copy link
Collaborator

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.

@Dotnet-GitSync-Bot Dotnet-GitSync-Bot added the untriaged New issue has not been triaged by the area owner label Mar 20, 2020
@safern
Copy link
Member

safern commented Mar 20, 2020

cc: @ViktorHofer

@wli3
Copy link

wli3 commented Mar 20, 2020

@wli3
Copy link

wli3 commented Mar 20, 2020

could mitigate it for now

@ViktorHofer
Copy link
Member

A mitigation is already in process: #33871. Let's discuss the right fix in the sdk issue.

@janvorli
Copy link
Member

@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?

@jaredpar
Copy link
Member Author

@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.

@janvorli
Copy link
Member

@jaredpar that didn't help, the issue persists.

@jaredpar
Copy link
Member Author

@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.

@ghost ghost locked as resolved and limited conversation to collaborators Dec 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-Infrastructure blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' blocking-official-build untriaged New issue has not been triaged by the area owner
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants