Merge #542
542: More resilient `MoneroWalletRpc` startup in the harness r=da-kami a=da-kami Recently we se this problem on CI quite often: ``` May 27 01:26:55.898 INFO testcontainers::core::wait_for_message: Found message after comparing 80 lines May 27 01:27:00.858 INFO testcontainers::core::wait_for_message: Found message after comparing 2 lines May 27 01:27:00.859 INFO monero_harness: Starting monerod: DQma_monerod May 27 01:27:08.143 INFO testcontainers::core::wait_for_message: Found message after comparing 183 lines May 27 01:27:08.204 INFO monero_harness: Starting miner wallet: miner May 27 01:27:09.832 INFO testcontainers::core::wait_for_message: Found message after comparing 16 lines May 27 01:27:12.261 INFO monero_harness: Starting wallet: alice May 27 01:27:14.482 INFO testcontainers::core::wait_for_message: Found message after comparing 16 lines thread 'alice_punishes_after_restart_if_bob_dead' panicked at 'called `Result::unwrap()` on an `Err` value: error sending request for url (http://127.0.0.1:49177/json_rpc): operation was canceled: connection closed before message completed ``` Given the message `connection closed before message completed` it is likely that the `monero-wallet-rpc` is not fully started yet. Unfortunately we cannot wait to see a different message in the logs upon container startup, because there are just no further deterministic messages after the one we are currently listening on. To overcome this problem without extending testcontainers we introduce a retry mechanism when creating the wallet. Co-authored-by: Daniel Karzel <daniel@comit.network>pull/515/head
commit
60d595f6c7
Loading…
Reference in New Issue