Description
Is there an existing issue for this?
- I have searched the existing issues
Describe the bug
Recent change in dotnet runtime caused failures in dotnet-watch on Unix-based systems:
dotnet/docs#46226
The issue was addressed in dotnet-watch for scenarios where dotnet-watch injects agent into the running process that applies changes to the process. The agent now registers SIGTERM signal handler and terminates the process if no other signal handler does so.
Web scenario tests are still failing though. This is likely because dotnet-watch does not inject the agent into devserver and therefore won't handle POSIX signals for the process, or it does not implement the signal correctly.
See PR dotnet/sdk#49549.
Detailed test log for one of the tests. The port used by the web app is not being released when the process terminates and after restarting the app fails trying to use the same port.