mirror of
https://github.com/django/django.git
synced 2025-08-01 09:32:50 +00:00
[2.2.x] Fixed #28790 -- Doc'd how to avoid running certain test classes in parallel.
Backport of dafdfd6a60
from master
This commit is contained in:
parent
46a05e10a4
commit
5e91adc79d
2 changed files with 40 additions and 0 deletions
|
@ -1397,6 +1397,12 @@ Each process gets its own database. You must ensure that different test cases
|
|||
don't access the same resources. For instance, test cases that touch the
|
||||
filesystem should create a temporary directory for their own use.
|
||||
|
||||
.. note::
|
||||
|
||||
If you have test classes that cannot be run in parallel, you can use
|
||||
``SerializeMixin`` to run them sequentially. See :ref:`Enforce running test
|
||||
classes sequentially <topics-testing-enforce-run-sequentially>`.
|
||||
|
||||
This option requires the third-party ``tblib`` package to display tracebacks
|
||||
correctly:
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue