Browse Source

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 <rusty@rustcorp.com.au>
ppa-0.6.1
Rusty Russell 7 years ago
committed by Christian Decker
parent
commit
85a062164a
  1. 4
      tests/test_lightningd.py

4
tests/test_lightningd.py

@ -1472,8 +1472,8 @@ class LightningDTests(BaseLightningDTests):
c1 = self.executor.submit(l1.rpc.close, l2.info['id']) c1 = self.executor.submit(l1.rpc.close, l2.info['id'])
c2 = self.executor.submit(l2.rpc.close, l1.info['id']) c2 = self.executor.submit(l2.rpc.close, l1.info['id'])
# Wait for close to finish # Wait for close to finish
c1.result(10) c1.result(utils.TIMEOUT)
c2.result(10) c2.result(utils.TIMEOUT)
l1.daemon.wait_for_log('sendrawtx exit 0') l1.daemon.wait_for_log('sendrawtx exit 0')
# Get close confirmed # Get close confirmed
l1.bitcoin.generate_block(100) l1.bitcoin.generate_block(100)

Loading…
Cancel
Save