Replies: 3 comments 1 reply
-
|
These mostly look to be MSBuild worker nodes - these stay around on purpose, but they shouldn't be locking any assemblies since those assemblies should be unloaded after a build. If this is causing actual problems you should be able to force them all to shut down with |
Beta Was this translation helpful? Give feedback.
-
|
Interesting, I am seeing this: Building the solution again does resolve the problem. |
Beta Was this translation helpful? Give feedback.
-
|
So, at this point, we don't do anything extra, just a normal |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Apologies for not reporting this sooner but I fear I still found a problem after #14677.
Repro steps
dotnet build Fsharp.Compiler.Service.slnGet-Process -Name "dotnet" | Select-Object Id,Name,StartTime,CommandLineExpected behavior
There shouldn't be any lingering dotnet processes after that initial build.
When doing a rebuild or
-c Releasefslexcould be stuck because of a lock.Actual behavior
Known workarounds
Kill all the processes:
Get-Process -Name "dotnet" | KillBeta Was this translation helpful? Give feedback.
All reactions