pytest: fix up test_zeroconf_multichan_forward once routehints fixed.

After this, the invoice (correctly!) gives the zeroconf channel as a routehint,
so this test fails.  Simple workaround: make invoice before creating zeroconf
channel.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
This commit is contained in:
Rusty Russell 2024-01-30 04:51:12 +10:30
parent 412bb137e0
commit a27bbbb734

View file

@ -2076,6 +2076,9 @@ def test_zeroconf_multichan_forward(node_factory):
# Just making sure the allowlisted node_id matches.
assert l2.info['id'] == node_id
# Create invoice which doesn't use zeroconf channel as routehint!
inv = l3.rpc.invoice(amount_msat=10000, label='lbl1', description='desc')['bolt11']
# Now create a channel that is twice as large as the real channel,
# and don't announce it.
l2.fundwallet(10**7)
@ -2084,7 +2087,6 @@ def test_zeroconf_multichan_forward(node_factory):
l2.daemon.wait_for_log(r'peer_in WIRE_CHANNEL_READY')
l3.daemon.wait_for_log(r'peer_in WIRE_CHANNEL_READY')
inv = l3.rpc.invoice(amount_msat=10000, label='lbl1', description='desc')['bolt11']
l1.rpc.pay(inv)
for c in l2.rpc.listpeerchannels(l3.info['id'])['channels']: