test_lightningd.py: fix timing error in test_forward_different_fees_and_cltv

We need to make sure all the updates are known to gossip.  Since
one is the local update, we change that message to look the same.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
This commit is contained in:
Rusty Russell 2018-01-12 14:40:00 +10:30 committed by Christian Decker
parent d84dc5633a
commit 6b7b7f1007
2 changed files with 6 additions and 3 deletions

View file

@ -790,7 +790,9 @@ static void handle_local_add_channel(struct peer *peer, u8 *msg)
c->htlc_minimum_msat = htlc_minimum_msat;
c->base_fee = fee_base_msat;
c->proportional_fee = fee_proportional_millionths;
status_trace("Added and updated local channel %s/%d", type_to_string(msg, struct short_channel_id, &scid), direction);
status_trace("Channel %s(%d) was updated (LOCAL)",
type_to_string(msg, struct short_channel_id, &scid),
direction);
}
/**

View file

@ -1614,8 +1614,9 @@ class LightningDTests(BaseLightningDTests):
# Make sure l1 has seen announce for all channels.
l1.daemon.wait_for_logs([
'Channel {}\\(0\\) was updated.'.format(c1),
'Channel {}\\(1\\) was updated.'.format(c1),
# One of the first two is LOCAL (has (LOCAL) at end of msg)
'Channel {}\\(0\\) was updated'.format(c1),
'Channel {}\\(1\\) was updated'.format(c1),
'Channel {}\\(0\\) was updated.'.format(c2),
'Channel {}\\(1\\) was updated.'.format(c2)])