summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorR. David Murray <rdmurray@bitdance.com>2009-11-11 18:07:27 (GMT)
committerR. David Murray <rdmurray@bitdance.com>2009-11-11 18:07:27 (GMT)
commitfdd53545a153b8743657656dbc5d3e27b0faebfb (patch)
treef92c4b3a2302f3b40665f9e7039b24696f475f5b
parent5dff3544f3b3b43f739b8ca02a8f1391e9128bb5 (diff)
downloadcpython-fdd53545a153b8743657656dbc5d3e27b0faebfb.zip
cpython-fdd53545a153b8743657656dbc5d3e27b0faebfb.tar.gz
cpython-fdd53545a153b8743657656dbc5d3e27b0faebfb.tar.bz2
I got the relative magnitudes of the timeout increases reversed, so
I'm bumping up the longer test to the 60 seconds I intended to make it. If this doesn't cure the intermittent buildbot timeouts, I'm going to turn that test into a warning rather than a failure.
-rw-r--r--Lib/bsddb/test/test_replication.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/Lib/bsddb/test/test_replication.py b/Lib/bsddb/test/test_replication.py
index faeaf46..8e8309b 100644
--- a/Lib/bsddb/test/test_replication.py
+++ b/Lib/bsddb/test/test_replication.py
@@ -116,7 +116,7 @@ class DBReplicationManager(unittest.TestCase):
# is not generated if the master has no new transactions.
# This is solved in BDB 4.6 (#15542).
import time
- timeout = time.time()+30
+ timeout = time.time()+60
while (time.time()<timeout) and not (self.confirmed_master and self.client_startupdone) :
time.sleep(0.02)
# this fails on Windows as self.client_startupdone never gets set