Handle failed conversion gracefully
GitHub Actions / Test Results (Integration tests)
failed
Sep 1, 2023 in 0s
1 fail, 26 pass in 14m 12s
Annotations
github-actions / Test Results (Integration tests)
1 out of 2 runs failed: Scenario: Simple propagation: tests/features/Propagation.feature:26:3
artifacts/junit-cucumber/cucumber-output-junit.xml [took 9s]
Raw output
Step panicked. Captured output: called `Result::unwrap()` on an `Err` value: transport error Caused by: 0: error trying to connect: tcp connect error: Connection refused (os error 111) 1: tcp connect error: Connection refused (os error 111) 2: Connection refused (os error 111)
Scenario: Simple propagation
✔ Given I have 2 seed nodes
✔ When I have 4 base nodes connected to all seed nodes
✔ When I have a SHA3 miner MINER connected to all seed nodes
✔ When mining node MINER mines 5 blocks
✔ Then node MINER is at height 5
✘ Then all nodes are at height 5
Step failed:
Defined: tests/features/Propagation.feature:32:5
Matched: integration_tests/tests/steps/node_steps.rs:166:1
Step panicked. Captured output: called `Result::unwrap()` on an `Err` value: transport error
Caused by:
0: error trying to connect: tcp connect error: Connection refused (os error 111)
1: tcp connect error: Connection refused (os error 111)
2: Connection refused (os error 111)
Client {
base_nodes: {},
blocks: {},
miners: {
"MINER": MinerProcess {
name: "MINER",
base_node_name: "MINER",
wallet_name: "MINER",
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: {},
seed_nodes: [
"seed_node_0",
"seed_node_1",
],
wallet_tx_ids: {},
errors: [],
last_imported_tx_ids: [],
last_merge_miner_response: Null,
}
Check notice on line 0 in .github
github-actions / Test Results (Integration tests)
27 tests found
There are 27 tests, see "Raw output" for the full list of tests.
Raw output
Scenario: A message is propagated between clients via 3rd party: tests/features/ChatFFI.feature:7:3
Scenario: As a client I want to receive a one-sided transaction: tests/features/WalletFFI.feature:212:5
Scenario: As a client I want to receive contact liveness events: tests/features/WalletFFI.feature:73:5
Scenario: As a client I want to retrieve a list of transactions I have made and received: tests/features/WalletFFI.feature:96:5
Scenario: As a client I want to retrieve the mnemonic word list for a given language: tests/features/WalletFFI.feature:24:5
Scenario: As a client I want to send a one-sided transaction: tests/features/WalletFFI.feature:175:5
Scenario: As a wallet I want to submit a transaction: tests/features/WalletQuery.feature:18:3
Scenario: As a wallet send to a wallet connected to a different base node: tests/features/WalletTransfer.feature:9:3
Scenario: Callback for new message received: tests/features/ChatFFI.feature:14:3
Scenario: Clear out mempool: tests/features/Mempool.feature:46:3
Scenario: Create burn transaction: tests/features/WalletTransactions.feature:411:3
Scenario: Node rolls back reorg on invalid block: tests/features/Reorgs.feature:63:3
Scenario: Pruned mode simple sync: tests/features/Sync.feature:50:3
Scenario: Pruned node should handle burned output: tests/features/Sync.feature:61:3
Scenario: Pruned node should prune outputs: tests/features/Propagation.feature:92:3
Scenario: Simple block sync: tests/features/Sync.feature:26:3
Scenario: Simple propagation: tests/features/Propagation.feature:26:3
Scenario: Simple reorg to stronger chain: tests/features/Reorgs.feature:8:3
Scenario: Simple reorg with burned output: tests/features/Reorgs.feature:33:3
Scenario: Sync burned output: tests/features/Sync.feature:34:3
Scenario: Syncing node while also mining before tip sync: tests/features/Sync.feature:142:5
Scenario: Transactions are propagated through a network: tests/features/Mempool.feature:8:3
Scenario: Verify UTXO and kernel MMR size in header: tests/features/BlockTemplate.feature:8:1
Scenario: Wallet recovery with connected base node staying online: tests/features/WalletRecovery.feature:8:5
Scenario: Wallet sending and receiving one-sided transactions: tests/features/WalletTransactions.feature:8:3
Scenario: When a new node joins the network, it receives all peers: tests/features/Sync.feature:77:3
Scenario: Zero-conf transactions: tests/features/Mempool.feature:124:3
Loading