From a4dd523c8b2c3586fc64e2ff30ed40dfbe94fd49 Mon Sep 17 00:00:00 2001 From: Rusty Russell Date: Fri, 12 Jan 2018 13:58:53 +1030 Subject: [PATCH] test_lightning.py: fix ambigious log order in test_reconnect_signed. Signed-off-by: Rusty Russell --- tests/test_lightningd.py | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/tests/test_lightningd.py b/tests/test_lightningd.py index 5d9532ce0..b0b2b0996 100644 --- a/tests/test_lightningd.py +++ b/tests/test_lightningd.py @@ -1964,11 +1964,9 @@ class LightningDTests(BaseLightningDTests): assert l1.rpc.getpeer(l2.info['id'])['peerid'] == l2.info['id'] assert l2.rpc.getpeer(l1.info['id'])['peerid'] == l1.info['id'] - # Technically, this is async to fundchannel. - l1.daemon.wait_for_log('sendrawtx exit 0') - - # Wait for reconnect, awaiting lockin.. - l1.daemon.wait_for_log('Peer has reconnected, state CHANNELD_AWAITING_LOCKIN') + # Technically, this is async to fundchannel (and could reconnect first) + l1.daemon.wait_for_logs(['sendrawtx exit 0', + 'Peer has reconnected, state CHANNELD_AWAITING_LOCKIN']) l1.bitcoin.generate_block(6)