GitHub Actions / Test Results (Integration tests)
failed
Aug 29, 2023 in 0s.
View latest attempt.
4 fail, 23 pass in 27m 32s
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 17s]
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,
}
github-actions / Test Results (Integration tests)
1 out of 2 runs failed: Scenario: Wallet sending and receiving one-sided transactions: tests/features/WalletTransactions.feature:8:3
artifacts/junit-cucumber/cucumber-output-junit.xml [took 9m 50s]
Raw output
Step panicked. Captured output: wallet WALLET_B failed to get less balance than amount 1100000, current amount is 2000000
Scenario: Wallet sending and receiving one-sided transactions
✔ Given I have a seed node NODE
✔ When I have 1 base nodes connected to all seed nodes
✔ 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 wallet WALLET_C 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 15 blocks
✔ Then all nodes are at height 15
✔ When I wait 5 seconds
✔ When I wait for wallet WALLET_A to have at least 55000000000 uT
✔ Then I send a one-sided transaction of 1000000 uT from WALLET_A to WALLET_B at fee 100
✔ Then I send a one-sided transaction of 1000000 uT from WALLET_A to WALLET_B at fee 100
✔ When mining node MINER mines 5 blocks
✔ Then all nodes are at height 20
✔ Then I wait for wallet WALLET_B to have at least 2000000 uT
✔ Then I send 900000 uT from wallet WALLET_B to wallet WALLET_B at fee 20
✘ Then I wait for wallet WALLET_B to have less than 1100000 uT
Step failed:
Defined: tests/features/WalletTransactions.feature:26:5
Matched: integration_tests/tests/steps/wallet_steps.rs:2025:1
Step panicked. Captured output: wallet WALLET_B failed to get less balance than amount 1100000, current amount is 2000000
Client {
base_nodes: {},
blocks: {},
miners: {
"MINER": MinerProcess {
name: "MINER",
base_node_name: "NODE",
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",
"WALLET_B": "NODE",
"WALLET_C": "NODE",
},
seed_nodes: [
"NODE",
],
wallet_tx_ids: {
"944f39630e78e3ea8fe5e857625fb1b88a8f0740c7d4894632da30dc1200f33c5f": [
1226885579098958208,
9665148305380385863,
],
"84e884167c7228c8494510b2444d64d3451ba56cd8d519f56f065504f028be0ff9": [
1226885579098958208,
9665148305380385863,
12944050409989517323,
12944050409989517323,
],
},
errors: [],
last_imported_tx_ids: [],
last_merge_miner_response: Null,
}
github-actions / Test Results (Integration tests)
1 out of 2 runs failed: Scenario: Create burn transaction: tests/features/WalletTransactions.feature:411:3
artifacts/junit-cucumber/cucumber-output-junit.xml [took 1m 3s]
Raw output
Step panicked. Captured output: Wallet WALLET_A failed to detect tx with tx_id = 10964253251892933611 to be Mined_Confirmed, current status is MinedUnconfirmed
Scenario: Create burn transaction
✔ Given I have a seed node NODE
✔ When I have 2 base nodes connected to all seed nodes
✔ 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_A connected to base node NODE and wallet WALLET_A
✔ When I have mining node MINER_B connected to base node NODE and wallet WALLET_B
✔ When mining node MINER_A mines 12 blocks
✔ When mining node MINER_B mines 3 blocks
✔ Then all nodes are at height 15
✔ When I wait for wallet WALLET_A to have at least 221552530060 uT
✔ When I create a burn transaction of 201552500000 uT from WALLET_A at fee 100
✔ When mining node MINER_B mines 5 blocks
✔ Then all nodes are at height 20
✘ Then wallet WALLET_A detects all transactions as Mined_Confirmed
Step failed:
Defined: tests/features/WalletTransactions.feature:425:5
Matched: integration_tests/tests/steps/wallet_steps.rs:155:1
Step panicked. Captured output: Wallet WALLET_A failed to detect tx with tx_id = 10964253251892933611 to be Mined_Confirmed, current status is MinedUnconfirmed
Client {
base_nodes: {},
blocks: {},
miners: {
"MINER_A": MinerProcess {
name: "MINER_A",
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",
},
seed_nodes: [
"NODE",
],
wallet_tx_ids: {},
errors: [],
last_imported_tx_ids: [],
last_merge_miner_response: Null,
}
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 29s]
Raw output
Step panicked. Captured output: Service on port 18164 never started
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
Step failed:
Defined: tests/features/WalletTransfer.feature:12:5
Matched: integration_tests/tests/steps/node_steps.rs:49:1
Step panicked. Captured output: Service on port 18164 never started
Client {
base_nodes: {},
blocks: {},
miners: {},
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_A",
"SEED_B",
],
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