-
Notifications
You must be signed in to change notification settings - Fork 252
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
[Bug]: MSB4242: SDK Resolver Failure due to System.Threading.AbandonedMutexException #12159
Comments
Same error is reported in the following 2 GitHub action runs. |
Sorry for the inconvenience caused by this bug. For folks who are hitting this issue, as a workaround, would it be possible to execute |
I just ran into another failure that seems like it could be related (this is with the aforementioned workaround applied): https://github.com/vezel-dev/niru/actions/runs/3260762897/jobs/5354602659#step:4:15
This one seems rare - it's the first time I've seen it since applying the workaround and it didn't happen on a subsequent run. |
The workaround has been working in our environment so far, thanks. |
I initially reported here: https://developercommunity.visualstudio.com/t/NuGet---race-condition-NuGetCommonMigr/10175710 |
Thanks for getting this fixed! Our team just ran into it as well. Is there a good place to set up a notification for when this ships? Or a particular dotnet SDK version it'll end up in we can watch out for? |
As far as I know, customers can hit this bug only if they have multiple projects trying to download custom SDKs using NuGet resolver functionality. |
Yes, we have multiple projects trying to download custom SDKs using NuGet. |
@breidikl @cliffchapmanrbx @alexrp @VemundH @brunolins16 - sorry for the direct ping. This issue is fixed in preview versions of .NET 8. Would it be possible to install preview versions of .NET 8 & check whether the restore succeeds or not? Thanks for your help in advance. |
Thank you for the information! Our current automation harness makes it a little difficult to test this in-situ, I will see if we can construct an isolated environment to test it. |
@kartheekp-ms Is that issue fixed in .NET 7 as well? |
@brunolins16 - Not yet. The fix is currently in .NET 8 preview versions. Hence asking the community to help us to validate the fix by installing .NET 8 preview version. |
NuGet's CI build also failed with this error message while running cross verification tests job.
|
Another NuGet's CI build also failed with this error message while running cross verify tests job.
cc @dominoFire |
Another NuGet's CI build failed with the same error message. cc @erdembayar |
@kartheekp-ms we are getting different errors during the migrations. Do you think it is related? Pipeline:
|
@brunolins16 - A similar was issue reported in dotnet/runtime#78062 (comment). May be this error has the same root cause mentioned in dotnet/runtime#36823 which was created as a follow-up for PowerShell/PSReadLine#1464. |
Got the same error in devops pipeline. Error seems related, in my case, to 'tools' that comes with 'ubuntu-latest' image : No error running: Fails when running: FIX in my situation. Changed from ubuntu-latest to ubuntu-20.04 and installed net6.0 and net7.0 in seperate steps:
ERROR: AFTER FIX: Time Elapsed 00:00:07.74 Build succeeded. |
The patch fixing this issue has been released in February 2023 .NET SDK servicing release. https://dotnet.microsoft.com/en-us/download/dotnet/6.0 |
NuGet Product Used
dotnet.exe
Product Version
SDK 6.0.402
Worked before?
No response
Impact
I'm unable to use this version
Repro Steps & Context
Tracking issue for dotnet/sdk#28488. Essentially, this issue can be hit if solution has multiple projects trying to download custom SDKs using NuGet resolver functionality.
Verbose Logs
No response
The text was updated successfully, but these errors were encountered: