From 798d9354f679292a23c825a865097e9f0e3d105f Mon Sep 17 00:00:00 2001
From: Peter Stachowski <peter@tesora.com>
Date: Mon, 18 Jul 2016 17:48:08 +0000
Subject: [PATCH] Serialize py34 tests

It turns out that the way the python34 tests are run in parallel is
to spin up several processes (not threads).  This means that putting
locks around creating the database in a single 'run' would need an
inter-process lock not a thread lock.

While the feasibility of this is investigated, change the behaviour
of the tests to run in series to increase stability.

On a 4 cpu test machine this only increased the run time by 70s.

Partially implements: blueprint trove-python3

Change-Id: I530fcf22b697148a3d0a286015c5a79481528d8e
---
 tox.ini | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tox.ini b/tox.ini
index 66466d9d68..5ea44fd46a 100644
--- a/tox.ini
+++ b/tox.ini
@@ -28,7 +28,7 @@ commands =
 
 [testenv:py34]
 commands =
-    ostestr --blacklist_file=blacklist-py3.txt
+    ostestr --blacklist_file=blacklist-py3.txt --serial
 
 
 [testenv:debug]