#31509: Enable faulthandler automatically during tests
-------------------------------------+-------------------------------------
Reporter: Adam (Chainz) | Owner: Omkar
Johnson | Kulkarni
Type: New feature | Status: assigned
Component: Testing framework | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Omkar Kulkarni):
Sorry, I think I was unclear in my previous comment. I was sending SIGABRT
to the child process that was forked, but I also tested it using
os.kill(os.getpid(), SIGSEGV/SIGABRT) (for both parallel and serial
tests). It works properly in parallel only if the child processes are
forked. If multiprocessing.get_start_method() == 'spawn', then the
faulthandler doesn't output the trace. According to the comments in
runner.py, it seems like Django's parallel test runner relies on the
processes being forked, but I can figure out a way to make it work for
'spawn' if that is a valid use case.
--
Ticket URL: <https://code.djangoproject.com/ticket/31509#comment:8>
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/068.1fc76c001bf1eefbeee690980f8c4735%40djangoproject.com.
