chore: new release for esme v1.9.0-pre.0 (#6688) #1764
GitHub Actions / JUnit Test Report
failed
Nov 19, 2024 in 0s
24 tests run, 23 passed, 0 skipped, 1 failed.
Annotations
Check failure on line 1 in feature:8:5
github-actions / JUnit Test Report
feature:8:5.Scenario: Wallet recovery with connected base node staying online: tests/features/WalletRecovery.feature:8:5
Step panicked. Captured output: Service 'Tcp' on port '18478' never started for 'WALLET_D'
Raw output
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:91:1
Step panicked. Captured output: Service 'Tcp' on port '18478' never started for 'WALLET_D'
Client {
base_nodes: {},
blocks: {},
miners: {
"MINER": MinerProcess {
name: "MINER",
base_node_name: "NODE",
wallet_name: "WALLET_A",
mine_until_height: 100000,
stealth: false,
},
"MINER_B": MinerProcess {
name: "MINER_B",
base_node_name: "NODE",
wallet_name: "WALLET_B",
mine_until_height: 100000,
stealth: false,
},
},
ffi_wallets: {},
wallets: {},
merge_mining_proxies: {},
transactions: {},
stopped_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,
}
Loading