Tests: Explicitly set multiprocessing start method to "fork"#405
Merged
Tests: Explicitly set multiprocessing start method to "fork"#405
Conversation
By using multiprocessing's ForkProcess, the testsuite will also start working on macOS again, even on Python 3.8+. The background on this is that beginning with Python 3.8+, "fork" is not the default on all platforms anymore but has been changed to "spawn" on macOS. This method, however, apparently is not compatible with how multiprocessing is currently used within the test harness.
seut
approved these changes
Mar 26, 2021
Member
seut
left a comment
seut
left a comment
There was a problem hiding this comment.
Great! Thanks for tracking this down.
This was referenced Mar 26, 2021
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Hi there,
because @mfussenegger said at #386 (comment):
this patch provides a better alternative than my initial attempts at #386, as it tries to tackle the underlying root cause of one detail which made the testsuite croak on macOS. Specifically, it resolves #398.
By using multiprocessing's ForkProcess, the testsuite will also start working on macOS again, even on Python 3.8+.
The background on this is that beginning with Python 3.8+, "fork" is not the default on all platforms anymore but has been changed to "spawn" on macOS. This method, however, apparently is not compatible with how multiprocessing is currently used within the test harness.
With kind regards,
Andreas.