summaryrefslogtreecommitdiff
path: root/tox.ini
diff options
context:
space:
mode:
authorDamien Lespiau <damien.lespiau@intel.com>2015-09-22 17:11:49 +0100
committerStephen Finucane <stephen.finucane@intel.com>2015-11-05 04:21:02 +0000
commit266601e4943e04dbc0755382ebaa7129a28d9f03 (patch)
tree3549ffc2ebf156fc4f0433313254b322d5af11f7 /tox.ini
parent7297e509222854b88a5a220c2f092bfb863aad0f (diff)
downloadpatchwork-266601e4943e04dbc0755382ebaa7129a28d9f03.tar
patchwork-266601e4943e04dbc0755382ebaa7129a28d9f03.tar.gz
tox: Use a range of ports for live servers
From: https://docs.djangoproject.com/en/1.8/topics/testing/tools/#liveservertestcase In the case where the tests are run by multiple processes in parallel (for example, in the context of several simultaneous continuous integration builds), the processes will compete for the same address, and therefore your tests might randomly fail with an "Address already in use" error. For example: Traceback (most recent call last): File ".../python2.7/site-packages/django/test/testcases.py", line 1193, in setUpClass raise cls.server_thread.error error: [Errno 98] Address already in use Signed-off-by: Damien Lespiau <damien.lespiau@intel.com> Acked-by: Stephen Finucane <stephen.finucane@intel.com>
Diffstat (limited to 'tox.ini')
-rw-r--r--tox.ini3
1 files changed, 2 insertions, 1 deletions
diff --git a/tox.ini b/tox.ini
index 19606e5..e44c884 100644
--- a/tox.ini
+++ b/tox.ini
@@ -14,7 +14,8 @@ deps =
setenv =
DJANGO_SETTINGS_MODULE = patchwork.settings.dev
commands =
- {toxinidir}/manage.py test --noinput '{posargs:patchwork}'
+ {toxinidir}/manage.py test --noinput --liveserver=localhost:9000-9200 \
+ '{posargs:patchwork}'
passenv =
http_proxy HTTP_PROXY https_proxy HTTPS_PROXY no_proxy NO_PROXY
PW_TEST_DB_USER PW_TEST_DB_PASS