From 85a062164a7d1c677a7192df396f142b1df66f2b Mon Sep 17 00:00:00 2001 From: Rusty Russell Date: Fri, 18 May 2018 15:19:16 +0930 Subject: [PATCH] test_lightningd: test_closing_torture timeout increase. I hit this timeout on pytest and valgrind with -n5; use the timeout variable from utils. Signed-off-by: Rusty Russell --- tests/test_lightningd.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tests/test_lightningd.py b/tests/test_lightningd.py index c92d3a887..5470a4e18 100644 --- a/tests/test_lightningd.py +++ b/tests/test_lightningd.py @@ -1472,8 +1472,8 @@ class LightningDTests(BaseLightningDTests): c1 = self.executor.submit(l1.rpc.close, l2.info['id']) c2 = self.executor.submit(l2.rpc.close, l1.info['id']) # Wait for close to finish - c1.result(10) - c2.result(10) + c1.result(utils.TIMEOUT) + c2.result(utils.TIMEOUT) l1.daemon.wait_for_log('sendrawtx exit 0') # Get close confirmed l1.bitcoin.generate_block(100)