Bump up timeout delays some more in timeouts isolation test.

The buildfarm members using -DCLOBBER_CACHE_ALWAYS still don't like this
test.  Some experimentation shows that on my machine, isolationtester's
query to check for "waiting" state takes 2 to 2.5 seconds to bind+execute
under -DCLOBBER_CACHE_ALWAYS.  Set the timeouts to 5 seconds to leave some
headroom for possibly-slower buildfarm critters.

Really we ought to fix the "waiting" query, which is not only horridly
slow but outright wrong in detail; and then maybe we can back off these
timeouts.  But right now I'm just trying to get the buildfarm green again.

1 files changed, 4 insertions, 4 deletions

diff --git a/src/test/isolation/specs/timeouts.spec b/src/test/isolation/specs/timeouts.spec
index 39bcf0cc819..7f821d44d0e 100644
--- a/src/test/isolation/specs/timeouts.spec
+++ b/src/test/isolation/specs/timeouts.spec
@@ -19,10 +19,10 @@ teardown	{ ABORT; }
 
 session "s2"
 setup		{ BEGIN ISOLATION LEVEL READ COMMITTED; }
-step "sto"	{ SET statement_timeout = 2000; }
-step "lto"	{ SET lock_timeout = 2000; }
-step "lsto"	{ SET lock_timeout = 2000; SET statement_timeout = 3000; }
-step "slto"	{ SET lock_timeout = 3000; SET statement_timeout = 2000; }
+step "sto"	{ SET statement_timeout = 5000; }
+step "lto"	{ SET lock_timeout = 5000; }
+step "lsto"	{ SET lock_timeout = 5000; SET statement_timeout = 6000; }
+step "slto"	{ SET lock_timeout = 6000; SET statement_timeout = 5000; }
 step "locktbl"	{ LOCK TABLE accounts; }
 step "update"	{ DELETE FROM accounts WHERE accountid = 'checking'; }
 teardown	{ ABORT; }