We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Example at: https://github.com/jonathanpeppers/inclusive-code-reviews-ml/actions/runs/8113476182/job/22176866347?pr=166
This could be a bug in GitHub actions, but the log says:
Terminate orphan process: pid (2202) (dotnet) Terminate orphan process: pid (2243) (dotnet)
Then at the bottom, it is stuck on:
Cleaning up orphan processes
I'm seeing this also on other builds (that are doing dotnet build), so it appears GitHub actions doesn't like dotnet starting daemon-like processes.
dotnet build
Is there an env var we should set to prevent dotnet processes from staying alive?
dotnet
The text was updated successfully, but these errors were encountered:
That might be the compiler server. I'm not if there's a way to disable it.
Sorry, something went wrong.
The run above took 15 minutes, and I thought it was actually stuck... Seems like a general GitHub actions bug.
So the only "nice to have" is if there is an env var to disable the compiler server. It would probably save a second or two.
Shut down any build servers after we're done.
c4a3c85
Hopefully fixes #12.
Shut down any build servers after we're done. (#13)
af50909
Successfully merging a pull request may close this issue.
Example at: https://github.com/jonathanpeppers/inclusive-code-reviews-ml/actions/runs/8113476182/job/22176866347?pr=166
This could be a bug in GitHub actions, but the log says:
Then at the bottom, it is stuck on:
I'm seeing this also on other builds (that are doing
dotnet build
), so it appears GitHub actions doesn't like dotnet starting daemon-like processes.Is there an env var we should set to prevent
dotnet
processes from staying alive?The text was updated successfully, but these errors were encountered: