aljaz/lightning
1
0
Fork 0
mirror of https://github.com/aljazceru/lightning.git synced 2025-12-20 23:54:22 +01:00
Code Issues Packages Projects Releases Wiki Activity

pytest: give more time for test_closing_torture.

Browse Source 
The logs in various Travis failures show that it takes 20 seconds just for
closingd to read the init message.  As a result, the close times out (default
is 30 seconds).

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
This commit is contained in:
Rusty Russell
2018-07-28 11:26:36 +09:30
committed by Christian Decker
parent 9e14d6cf04
commit 65103ac426
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
tests/test_lightningd.py
View File

@@ -1489,9 +1489,9 @@ class LightningDTests(BaseLightningDTests):
l1.daemon.wait_for_logs(['to CHANNELD_NORMAL']) l1.daemon.wait_for_logs(['to CHANNELD_NORMAL'])
l2.daemon.wait_for_logs(['to CHANNELD_NORMAL']) l2.daemon.wait_for_logs(['to CHANNELD_NORMAL'])
# Start closers. # Start closers: can take a long time under valgrind!
c1 = self.executor.submit(l1.rpc.close, l2.info['id']) c1 = self.executor.submit(l1.rpc.close, l2.info['id'], False, 60)
c2 = self.executor.submit(l2.rpc.close, l1.info['id']) c2 = self.executor.submit(l2.rpc.close, l1.info['id'], False, 60)
# Wait for close to finish # Wait for close to finish
c1.result(utils.TIMEOUT) c1.result(utils.TIMEOUT)
c2.result(utils.TIMEOUT) c2.result(utils.TIMEOUT)