Message 387832 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	ned.deily
Recipients	ayesjm, jaraco, ned.deily, ronaldoussoren
Date	2021-03-01.02:58:42
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1614567523.14.0.194413879067.issue30837@roundup.psfhosted.org>
In-reply-to

Content
If the crashes are occurring while the multiprocessing fork tests are running, it's likely the issue described in Issue33725. In Python 3.8, the default start method for multiprocessing on macOS was changed to be "spawn" rather than "fork" because of the inherent issues with fork/no-exec on macOS. You could try backporting that to your 3.6. https://docs.python.org/3.8/library/multiprocessing.html#contexts-and-start-methods

If the crashes are occurring while the multiprocessing fork tests are running, it's likely the issue described in Issue33725. In Python 3.8, the default start method for multiprocessing on macOS was changed to be "spawn" rather than "fork" because of the inherent issues with fork/no-exec on macOS. You could try backporting that to your 3.6.

https://docs.python.org/3.8/library/multiprocessing.html#contexts-and-start-methods

History
Date	User	Action	Args
2021-03-01 02:58:43	ned.deily	set	recipients: + ned.deily, ronaldoussoren, jaraco, ayesjm
2021-03-01 02:58:43	ned.deily	set	messageid: <1614567523.14.0.194413879067.issue30837@roundup.psfhosted.org>
2021-03-01 02:58:43	ned.deily	link	issue30837 messages
2021-03-01 02:58:42	ned.deily	create