From fdd53545a153b8743657656dbc5d3e27b0faebfb Mon Sep 17 00:00:00 2001
From: "R. David Murray" <rdmurray@bitdance.com>
Date: Wed, 11 Nov 2009 18:07:27 +0000
Subject: [PATCH] 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.

---
 Lib/bsddb/test/test_replication.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Lib/bsddb/test/test_replication.py b/Lib/bsddb/test/test_replication.py
index faeaf4673d2..8e8309b97e3 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