Scenario: Wallet recovery with connected base node staying online
     Given I have a seed node NODE
     When I have wallet WALLET_A connected to all seed nodes
     When I have wallet WALLET_B connected to all seed nodes
     When I have mining node MINER connected to base node NODE and wallet WALLET_A
     When mining node MINER mines 10 blocks
     When I mine 5 blocks on NODE
     Then all nodes are at height 15
     When I have mining node MINER_B connected to base node NODE and wallet WALLET_B
     When mining node MINER_B mines 2 blocks
     When I mine 5 blocks on NODE
     Then all nodes are at height 22
     When I have wallet WALLET_D connected to all seed nodes
      Step failed:
      Defined: tests/features/WalletRecovery.feature:26:7
      Matched: integration_tests/tests/steps/wallet_steps.rs:85:1
      Step panicked. Captured output: Service on port 18555 never started
      Client {
          base_nodes: {},
          blocks: {},
          miners: {
              "MINER": MinerProcess {
                  name: "MINER",
                  base_node_name: "NODE",
                  wallet_name: "WALLET_A",
                  mine_until_height: 100000,
              },
              "MINER_B": MinerProcess {
                  name: "MINER_B",
                  base_node_name: "NODE",
                  wallet_name: "WALLET_B",
                  mine_until_height: 100000,
              },
          },
          ffi_wallets: {},
          wallets: {},
          merge_mining_proxies: {},
          chat_clients: [],
          transactions: {},
          wallet_addresses: {},
          utxos: {},
          output_hash: None,
          pre_image: None,
          wallet_connected_to_base_node: {
              "WALLET_A": "NODE",
              "WALLET_B": "NODE",
              "WALLET_D": "NODE",
          },
          seed_nodes: [
              "NODE",
          ],
          wallet_tx_ids: {},
          errors: [],
          last_imported_tx_ids: [],
          last_merge_miner_response: Null,
      }