tests/test_lightningd.py: fix assumption about gossip order

Reported-by: Christian Decker
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

tests/test_lightningd.py

@@ -327,11 +327,13 @@ class LightningDTests(BaseLightningDTests):
         assert not l1.daemon.is_in_log('peer_out WIRE_ANNOUNCEMENT_SIGNATURES')
 
         l1.bitcoin.rpc.generate(5)
-        l1.daemon.wait_for_log('peer_out WIRE_ANNOUNCEMENT_SIGNATURES')
-        l1.daemon.wait_for_log('peer_in WIRE_ANNOUNCEMENT_SIGNATURES')
+        # Could happen in either order.
+        l1.daemon.wait_for_logs(['peer_out WIRE_ANNOUNCEMENT_SIGNATURES',
+                                 'peer_in WIRE_ANNOUNCEMENT_SIGNATURES'])
 
-        l1.daemon.wait_for_log('peer_out WIRE_CHANNEL_ANNOUNCEMENT')
-        l1.daemon.wait_for_log('peer_in WIRE_CHANNEL_ANNOUNCEMENT')
+        # Could happen in either order.
+        l1.daemon.wait_for_logs(['peer_out WIRE_CHANNEL_ANNOUNCEMENT',
+                                 'peer_in WIRE_CHANNEL_ANNOUNCEMENT'])
 
         nodes = l1.rpc.getnodes()['nodes']
         assert set([n['nodeid'] for n in nodes]) == set([l1.info['id'], l2.info['id']])