#30806: Tox doesn't pass OBJC_DISABLE_INITIALIZE_FORK_SAFETY for MacOS test uns
-------------------------------------+-------------------------------------
Reporter: Christopher Wilcox | Owner:
| Christopher Wilcox
Type: Bug | Status: assigned
Component: Testing framework | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Dustin Harrison):
I was able to recreate this issue using MacOS Mojave 10.14.6, Python 3.7.3
Without OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES while the tests were
running the following messages would occasionally be emitted and
eventually the tests would hang:
{{{
[__NSPlaceholderDate initialize] may have been in progress in another
thread when fork() was called.
objc[40052]: +[__NSPlaceholderDate initialize] may have been in progress
in another thread when fork() was called. We cannot safely call it or
ignore it in the fork() child process. Crashing instead. Set a breakpoint
on objc_initializeAfterForkError to debug.
}}}
After applying my PR (https://github.com/django/django/pull/11830) and
running:
{{{
export OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES
tox
}}}
all tests pass and don't hang.
--
Ticket URL: <https://code.djangoproject.com/ticket/30806#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.16ba24068f306d408985511366668c22%40djangoproject.com.
