MarcoFalke fae3bf6b87 test: Avoid redundant stop and error spam on startup failure ...

Trying to immediately shut down a node after a startup failure without
waiting for the RPC to be fully up will in most cases just fail and lead
to an RPC error.

Also, it is confusing to sidestep the existing fallback to kill any
leftover nodes on a test failure.

So just rely on the fallback.

2025-01-08 11:09:49 +01:00

..

crypto

…

__init__.py

…

address.py

…

authproxy.py

test: report failure during utf8 response decoding

2024-11-11 10:45:01 -05:00

bdb.py

…

bip340_test_vectors.csv

…

blockfilter.py

…

blocktools.py

…

coverage.py

…

descriptors.py

…

key.py

…

mempool_util.py

assert_mempool_contents: assert not duplicates expected

2024-11-20 13:49:41 -05:00

messages.py

test: Avoid F541 (f-string without any placeholders)

2024-12-05 08:39:09 +01:00

netutil.py

…

p2p.py

test: Avoid logging error when logging error

2024-12-03 09:40:18 +01:00

psbt.py

…

script_util.py

…

script.py

…

segwit_addr.py

…

socks5.py

test: Avoid F541 (f-string without any placeholders)

2024-12-05 08:39:09 +01:00

test_framework.py

test: Avoid redundant stop and error spam on startup failure

2025-01-08 11:09:49 +01:00

test_node.py

test: Remove --noshutdown flag

2025-01-08 11:02:10 +01:00

test_shell.py

…

util.py

qa: Limit -maxconnections in tests

2024-12-19 15:04:22 +00:00

v2_p2p.py

…

wallet_util.py

…

wallet.py

…