From 817f7c703b4d9ae5b8d0d2a9c8a6f06f98e9412a Mon Sep 17 00:00:00 2001
From: Christian Decker <decker.christian@gmail.com>
Date: Fri, 10 Jul 2020 13:27:32 +0200
Subject: [PATCH] travis: Parallelize non-valgrind tests even if under
 developer

Tests were timing out, and there is no point in artificially limiting
ourselves if we can be quicker.
---
 .travis/build.sh | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/.travis/build.sh b/.travis/build.sh
index 734e5445a..d4fb1937c 100755
--- a/.travis/build.sh
+++ b/.travis/build.sh
@@ -12,9 +12,8 @@ export PATH=$CWD/dependencies/bin:"$HOME"/.local/bin:"$PATH"
 export PYTEST_PAR=2
 export PYTEST_SENTRY_ALWAYS_REPORT=1
 
-# If we're not in developer mode, tests spend a lot of time waiting for gossip!
-# But if we're under valgrind, we can run out of memory!
-if [ "$DEVELOPER" = 0 ] && [ "$VALGRIND" = 0 ]; then
+# Allow up to 4 concurrent tests when not under valgrind, which might run out of memory.
+if [ "$VALGRIND" = 0 ]; then
     PYTEST_PAR=4
 fi