From 7d8d2b56be12fd573dccba41cbeebfa2cea61534 Mon Sep 17 00:00:00 2001 From: Caio Ariede Date: Wed, 5 Jun 2019 11:35:36 -0300 Subject: [3.0.x] Fixed #28790 -- Doc'd how to avoid running certain test classes in parallel. Backport of dafdfd6a60638c4edcca7c4e65d11c0af654d759 from master --- docs/ref/django-admin.txt | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'docs/ref/django-admin.txt') diff --git a/docs/ref/django-admin.txt b/docs/ref/django-admin.txt index 1f76879c23..e665cebf8b 100644 --- a/docs/ref/django-admin.txt +++ b/docs/ref/django-admin.txt @@ -1418,6 +1418,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 `. + This option requires the third-party ``tblib`` package to display tracebacks correctly: -- cgit v1.3