Random error: Failed to resolve SDK 'package/version'. Package restore was successful but a package with the ID of "package" was not installed. #10935
Comments
We randomly run into a NuGet restore failure, which breaks the build, and is quite annoying. This might be due to a problem with multiple simultaneous restores, so this is an attempt to first restore the packages we need, in a single serialized restore, and once that's done we can process everything else in parallel. Ref: xamarin/maccore#2427 Ref: NuGet/Home#10935
) We randomly run into a NuGet restore failure, which breaks the build, and is quite annoying. This might be due to a problem with multiple simultaneous restores, so this is an attempt to first restore the packages we need, in a single serialized restore, and once that's done we can process everything else in parallel. Ref: xamarin/maccore#2427 Ref: NuGet/Home#10935
nkolev92
added
the
Product:MSBuildSDKResolver
|
Hey @rolfbjarne We have had issues like this in the past, #7817, but it seems like they were supposed to fixed. cc @jeffkl |
|
@nkolev92 the output is very different in the success case versus the failure case. Failure
Success
It does look like the restores are all happening at the same time and the locking is keeping them from all restoring the same package. But once the lock is released the package isn't there? @rolfbjarne what's the repository this is happening in? I'd like to look at the customized logic in use. |
|
We have some make logic here that executes 'dotnet pack' in parallel: https://github.com/xamarin/xamarin-macios/blob/0029ffa29d8396c35175befa8e414675b41774c9/dotnet/Makefile#L150. This is executed once for every The reference that causes problems is this one: https://github.com/xamarin/xamarin-macios/blob/0029ffa29d8396c35175befa8e414675b41774c9/dotnet/package/common.csproj#L52 |
Details about Problem
NuGet product used (NuGet.exe | Visual Studio | MSBuild.exe | dotnet.exe): dotnet
Product version: 6.0.100-preview.6.21280.2
Worked before? Don't know, this logic that runs into this problem is fairly new for us.
Repro steps and/or sample project
There are no repro steps, because it's random.
We see it somewhat frequently on CI, and trying again usually helps (but not always). It breaks our builds whenever it happens, so it's quite visible 😐
It might be related to running multiple dotnet processes in parallel. In fact some of these processes (they all do basically the same thing, just slightly different input) succeed, some fail.
Verbose Logs
This is a collection of binlogs (of all the dotnet processes that ran in parallel):
nupkgs.zip
The larger ones succeeded, the smaller ones didn't:
Example output from one of the failed ones:
it looks like the succeeding ones took a different code path:
The text was updated successfully, but these errors were encountered: