From 22c962bbc215180809004ed751fc447c7a0c6cf1 Mon Sep 17 00:00:00 2001 From: Zooko O'Whielacronx Date: Sat, 15 Aug 2009 09:05:12 -0700 Subject: [PATCH] tests: double the timeout on test_runner.RunNode.test_introducer since feisty hit a timeout 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 | 0 src/allmydata/test/test_runner.py | 2 +- 2 files changed, 1 insertion(+), 1 deletion(-) mode change 100755 => 100644 src/allmydata/nodemaker.py diff --git a/src/allmydata/nodemaker.py b/src/allmydata/nodemaker.py old mode 100755 new mode 100644 diff --git a/src/allmydata/test/test_runner.py b/src/allmydata/test/test_runner.py index 74f1e115..4d07e626 100644 --- a/src/allmydata/test/test_runner.py +++ b/src/allmydata/test/test_runner.py @@ -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() -- 2.45.2