id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
36596	"django_test_expected_failures has no effect on the parallel test runner in ""spawn"" mode"	Jacob Walls		"The [https://docs.djangoproject.com/en/5.2/releases/3.2/#database-backends django_test_expected_failures] attribute has no effect on the parallel test runner in ""spawn"" multiprocessing mode, because it uses `setattr` to [https://github.com/django/django/blob/4e7a991c12a113229e0927974d3bf94ea04eecf6/django/db/backends/base/creation.py#L365 monkey-patch] a class, and that patching is lost when workers are spawned.

To reproduce:
- add `multiprocessing.set_start_method(""spawn"")` near the top of runtests.py if not running on MacOS or Windows
- adjust postgres database settings to include `""OPTIONS"": { ""server_side_binding"": True}` (to trigger an expected failure),
- `./runtests.py aggregation.tests --settings=test_postgres --parallel=1` : passes
- `./runtests.py aggregation.tests --settings=test_postgres`: fails

Python will be defaulting all systems into ""spawn"" by default in Python 3.14, so we're about to see more traffic into this."	Bug	new	Testing framework	dev	Normal		multiprocessing	Tim Graham	Accepted	0	0	0	0	0	0