-
-
Notifications
You must be signed in to change notification settings - Fork 410
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
Backend null in epoll during CI run #4457
Comments
Our handler could be coming from a successful signal test run where we didn't dispose of the handler after the test completed successfully. |
The signal handler test in question is |
We should try running the tests and sending a SIGCHLD while they are running and see what happens... We believe the signal handling being triggered is related to SIGCHLD arriving but we arent certain. We need to run multiple times as WHEN the signal arrives in relation to our signal unit tests might be important. |
So here is the log output:
Note that are running code from signals/SignalHandler that leads to an asio event create which wou;ld mean we are creating a SignalHandler. But as far as I can see there's nothing in our tests that does that. I'm kind of confused.
Like #4438, this is happening at/hear shutdown of the program.
The text was updated successfully, but these errors were encountered: