tests: double the timeout on test_runner.RunNode.test_introducer since feisty hit...
authorZooko O'Whielacronx <zooko@zooko.com>
Sat, 15 Aug 2009 16:05:12 +0000 (09:05 -0700)
committerZooko O'Whielacronx <zooko@zooko.com>
Sat, 15 Aug 2009 16:05:12 +0000 (09:05 -0700)
I'm not sure if this is an actual timing issue (feisty is running on an overloaded VM if I recall correctly), or it there is a deeper bug.

src/allmydata/nodemaker.py [changed mode: 0755->0644]
src/allmydata/test/test_runner.py

old mode 100755 (executable)
new mode 100644 (file)
index 74f1e11533650b530738b559488fde0ffacb2d1d..4d07e626d42e4ec975e84822bd335697282d3669 100644 (file)
@@ -332,7 +332,7 @@ class RunNode(common_util.SignalMixin, unittest.TestCase, pollmixin.PollMixin,
             return res
         d.addBoth(_remove_hotline)
         return d
-    test_introducer.timeout = 240 # This hit the 120-second timeout on "François Lenny-armv5tel"
+    test_introducer.timeout = 480 # This hit the 120-second timeout on "François Lenny-armv5tel", then it hit a 240-second timeout on our feisty2.5 buildslave: http://allmydata.org/buildbot/builders/feisty2.5/builds/2381/steps/test/logs/test.log
 
     def test_client(self):
         self.skip_on_cygwin()