lightning

Christian Decker b7222531fe pytest: Stabilize the test_pay_direct test It was waiting for a remote channel, but not for all the interesting channels we want to check. It can sometimes happen that further away channels are added before closer ones are added, depending on propagation path, flush timers and bitcoind poll timers. This now just checks for all channels, which also reduces the ambiguity of whether we selected a path solely because we were lacking alternatives. Signed-off-by: Christian Decker <decker.christian@gmail.com>		6 years ago
..
benchmark.py	py-tests: rename 'announce' to 'wait_for_announce'	6 years ago
btcproxy.py	pytest: create proper mock failures.	6 years ago
conftest.py	pytest: Pass result to fixtures and keep directories of failed tests	7 years ago
fixtures.py	pytest: Have bitcoind own its proxies	6 years ago
requirements.txt	pytest: Update test dependencies to latest version	6 years ago
test_closing.py	misc: Update short_channel_id representation to use 'x' separators	6 years ago
test_connection.py	openingd/json_fund_channel:	6 years ago
test_gossip.py	pytest: Stabilize the test_pay_direct test	6 years ago
test_invoices.py	invoice: don't allow creation of unpayable invoices.	6 years ago
test_misc.py	jsonrpc: help, even for a single item, should be in an array.	6 years ago
test_pay.py	pytest: Stabilize the test_pay_direct test	6 years ago
test_plugin.py	plugins: get usage from plugins (required unless deprecated_apis == True).	6 years ago
utils.py	pytest: Stabilize the test_pay_direct test	6 years ago