You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In microsoft/testfx, we are producing an MSTest.Sdk, and we have integration tests for it.
It seems that when two tests are restoring in parallel, we may end up with the following
/mnt/vss/_work/1/s/artifacts/tmp/Debug/testsuite/dTeXr/VerifyMSTestAnalysisModeForDifferentAnalyzers/VerifyMSTestAnalysisModeForDifferentAnalyzers.csproj Could not resolve SDK "MSTest.Sdk". Exactly one of the probing messages below indicates why we could not resolve the SDK. Investigate and resolve that message to correctly specify the SDK.
SDK resolver "Microsoft.DotNet.MSBuildWorkloadSdkResolver" returned null.
Failed to resolve SDK 'MSTest.Sdk/3.8.0-ci'. Package restore was successful but a package with the ID of "MSTest.Sdk" was not installed.
What we do is simply we crate projects on disk, and we run dotnet build on them.
What I think could be happening is:
Two dotnet build invocations for two different projects that use MSTest.Sdk are done in parallel
First invocation finds the nupkg file (it's found locally, not from an online feed in our case). It starts extracting the nupkg
Two binlogs for the two dotnet build invocations that went in parallel (and sorry, one of them is run with Italian culture as it's a test for localization)
This hasn't been very high priority since the problem usually manifests when users are doing very custom things. Please upvote the other issue though as I'm hoping to have time to re-write the NuGet-based MSBuild project SDK resolver.
NuGet Product Used
dotnet.exe
Product Version
10.0.100-alpha.1.24573.1
Worked before?
Unknown, but unlikely that it worked before
Impact
It's more difficult to complete my work
Repro Steps & Context
In microsoft/testfx, we are producing an MSTest.Sdk, and we have integration tests for it.
It seems that when two tests are restoring in parallel, we may end up with the following
What we do is simply we crate projects on disk, and we run
dotnet build
on them.What I think could be happening is:
dotnet build
invocations for two different projects that use MSTest.Sdk are done in parallelTwo binlogs for the two
dotnet build
invocations that went in parallel (and sorry, one of them is run with Italian culture as it's a test for localization)binlogs.zip
Verbose Logs
The text was updated successfully, but these errors were encountered: