Deadlock in multiprocessing mode #344
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1 task
michprev
force-pushed
the
fix/multiprocess-testing-deadlock2
branch
from
b0daa8e to
900ce47
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Deadlock happens when the user types control + c and when the termination, the connection exception happens in the child wake process and it tries to open the debugger but it does not since the parent wake process waits until the child process ends.
So I make an exception handler not to open the debugger.
Related Tickets & Documents
I solve issues differently from #341 ; this solution ensures that no anvil ophan process is made and that no child process is forced to kill.
Related Issue #
Closes #
I clicked on "Allow edits from maintainers"