-
Notifications
You must be signed in to change notification settings - Fork 132
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
Containerized Alpine Job Hangs on dotnet build-server shutdown --vbcscompiler
#4796
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
1 similar comment
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
The suggestion from an internal team is to post the issue on stack overflow, so I opened https://stackoverflow.microsoft.com/questions/436123. I think it would still be helpful to have someone with more knowledge on the |
Was able to get some workarounds to help unblock this. I will be implementing those today. That said, the investigation is still ongoing. dotnet/sdk#45393 is needed to continue to investigation. |
This is a tracking issue describing a block related to the work in #4547.
Source-build builds hang when shutting down the VB/C# compiler build server via
dotnet build-server shutdown
ordotnet build-server shutdown --vbcscompiler
. This hanging only occurs in a containerized job using an Alpine with Node image. The hang occurs regardless of whether the build is internal or public, and it does not repro outside of a containerized azure devops job.Diagnostics so far:
dotnet exec VBCSCompiler.dll --shutdown
succeeds, allowing immediate subsequent calls todotnet build-server shutdown
ordotnet build-server shutdown --vbcscompiler
to finish. Note that if the server is started again, the build will hang when attempting to shutdown the server withoutdotnet exec VBCSCompiler.dll
.ulimit -u
returnsunlimited
.cc @jaredpar
The text was updated successfully, but these errors were encountered: