Browse Source
We had an intermittant test failure, where the fee we negotiated was further from our ideal than the final commitment transaction. It worked fine if the other side sent the mutual close first, but not if we sent our unilateral close first. ERROR: test_closing_different_fees (__main__.LightningDTests) ---------------------------------------------------------------------- Traceback (most recent call last): File "tests/test_lightningd.py", line 1319, in test_closing_different_fees wait_for(lambda: p.rpc.listpeers(l1.info['id'])['peers'][0]['channels'][0]['status'][1] == 'ONCHAIN:Tracking mutual close transaction') File "tests/test_lightningd.py", line 74, in wait_for raise ValueError("Error waiting for {}", success) ValueError: ('Error waiting for {}', <function LightningDTests.test_closing_different_fees.<locals>.<lambda> at 0x7f4b43e31a60>) Really, if we're prepared to negotiate it, we should be prepared to accept it ourselves. Simply take the cheapest tx which is above our minimum. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>ppa-0.6.1
committed by
Christian Decker
1 changed files with 4 additions and 19 deletions
Loading…
Reference in new issue