Wilmer Paulino 578df81fb2 lntest/itest: resolve mempool flake in multi-hop htlc local timeout test ... The test assumed that transactions would be broadcast and confirmed at incorrect heights. Due to timing issues, it was possible for the test to still succeed, resulting in a flake. The test assumes that Bob will sweep a pending outgoing HTLC and commit output back to their wallet. This commit ensures that these operations are done when expected, i.e.: 1. Bob force closes the channel due to the HTLC timing out. 2. Once the channel is confirmed, Bob broadcasts their HTLC timeout transaction. 3. Bob broadcasts their commit output sweep transaction once its CSV expires. 4. Bob broadcasts their second layer sweep transaction for the timed out HTLC once its CSV expires.		2019-08-30 12:15:14 -07:00
..
lnd_multi-hop_htlc_local_chain_claim_test.go	itest+routing: updating tests to account for BlockPadding	2019-07-23 21:03:30 -04:00
lnd_multi-hop_htlc_receiver_chain_claim_test.go	itest+routing: updating tests to account for BlockPadding	2019-07-23 21:03:30 -04:00
lnd_multi-hop_htlc_remote_chain_claim_test.go	itest+routing: updating tests to account for BlockPadding	2019-07-23 21:03:30 -04:00
lnd_test.go	lntest/itest: resolve mempool flake in multi-hop htlc local timeout test	2019-08-30 12:15:14 -07:00
onchain.go	lntest: add CPFP integration test	2019-06-11 15:06:41 -07:00