ExternalVendorCode/tahoe-lafs
1
0
Fork 0
mirror of https://github.com/tahoe-lafs/tahoe-lafs.git synced 2024-12-24 23:26:43 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

tests: double the timeout on test_runner.RunNode.test_introducer since feisty hit a timeout

Browse Source 
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.
This commit is contained in:
Zooko O'Whielacronx 2009-08-15 09:05:12 -07:00
parent d214f7eebe
commit 22c962bbc2
2 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

0
src/allmydata/nodemaker.py Executable file → Normal file
View File

2
src/allmydata/test/test_runner.py
View 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()