review comments
GitHub Actions / Test Results (Integration tests)
failed
Oct 24, 2023 in 0s
1 fail, 33 pass in 22m 45s
Annotations
github-actions / Test Results (Integration tests)
1 out of 2 runs failed: Scenario: As a wallet send to a wallet connected to a different base node: tests/features/WalletTransfer.feature:9:3
artifacts/junit-cucumber/cucumber-output-junit.xml [took 9m 13s]
Raw output
Step panicked. Captured output: Wallet WALLET_B failed to have at least 5T, it ended with 0T
Scenario: As a wallet send to a wallet connected to a different base node
✔ Given I have a seed node SEED_A
✔ When I have a seed node SEED_B
✔ When I have a base node NODE_A connected to all seed nodes
✔ When I have a base node NODE_B connected to all seed nodes
✔ When I have wallet WALLET_A with 10T connected to base node NODE_A
✔ When I have wallet WALLET_B connected to base node NODE_B
✔ When I wait 5 seconds
✔ When I transfer 5T from WALLET_A to WALLET_B
✔ When I mine 4 blocks on SEED_A
✔ Then wallet WALLET_A has 5T
✔ When I wait 5 seconds
✘ When wallet WALLET_B has 5T
Step failed:
Defined: tests/features/WalletTransfer.feature:21:5
Matched: integration_tests/tests/steps/wallet_steps.rs:1478:1
Step panicked. Captured output: Wallet WALLET_B failed to have at least 5T, it ended with 0T
Client {
base_nodes: {},
blocks: {},
miners: {
"temp_miner": MinerProcess {
name: "temp_miner",
base_node_name: "NODE_A",
wallet_name: "WALLET_A",
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_A",
"WALLET_B": "NODE_B",
},
seed_nodes: [
"SEED_A",
"SEED_B",
],
wallet_tx_ids: {
"6c6f563d1c0b47ae2f4c0301049b1836a70704f69094b50c75617f05c57b6016ae": [
17535028532752774778,
],
"e6920a817a700ec17a4fbba1a493444e1a120bf8041f293a4517ad76b009b801ce": [
17535028532752774778,
],
},
errors: [],
last_imported_tx_ids: [],
last_merge_miner_response: Null,
}
Check notice on line 0 in .github
github-actions / Test Results (Integration tests)
34 tests found
There are 34 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: A message receives a delivery receipt via FFI: tests/features/ChatFFI.feature:78:3
Scenario: A message receives a read receipt via FFI: tests/features/ChatFFI.feature:86: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 delivery confirmation received: tests/features/ChatFFI.feature:22:3
Scenario: Callback for new message received: tests/features/ChatFFI.feature:14:3
Scenario: Callback for read confirmation received: tests/features/ChatFFI.feature:31:3
Scenario: Chat shuts down without any errors: tests/features/ChatFFI.feature:63:3
Scenario: Clear out mempool: tests/features/Mempool.feature:46:3
Scenario: Create burn transaction: tests/features/WalletTransactions.feature:411:3
Scenario: Fetches all addresses from FFI conversations: tests/features/ChatFFI.feature:95: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: Reply to message: tests/features/ChatFFI.feature:68: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