fixup cucumber tests
GitHub Actions / Test Results (Integration tests)
failed
Nov 30, 2023 in 0s
5 fail, 27 pass in 1h 24m 32s
Annotations
github-actions / Test Results (Integration tests)
All 3 runs failed: Scenario: As a client I want to retrieve a list of transactions I have made and received: tests/features/WalletFFI.feature:96:5
artifacts/junit-ffi-cucumber/cucumber-output-junit.xml [took 8m 36s]
Raw output
Step panicked. Captured output: Transaction from SENDER to FFI_WALLET with amount 2000000 at fee 20 failed to be broadcasted
Scenario: As a client I want to retrieve a list of transactions I have made and received
✔ Given I have a seed node SEED
✔ When I have a base node BASE1 connected to all seed nodes
✔ When I have wallet SENDER connected to base node BASE1
✔ And I have a ffi wallet FFI_WALLET connected to base node BASE1
✔ When I add contact with alias ALIAS1 and address of SENDER to ffi wallet FFI_WALLET
✔ When I have wallet RECEIVER connected to base node BASE1
✔ When I have mining node MINER connected to base node BASE1 and wallet SENDER
✔ When mining node MINER mines 10 blocks
✔ Then all nodes are at height 10
✔ Then I wait for wallet SENDER to have at least 2000000 uT
✘ And I send 2000000 uT from wallet SENDER to wallet FFI_WALLET at fee 20
Step failed:
Defined: tests/features/WalletFFI.feature:108:9
Matched: integration_tests/tests/steps/wallet_steps.rs:839:1
Step panicked. Captured output: Transaction from SENDER to FFI_WALLET with amount 2000000 at fee 20 failed to be broadcasted
Client {
base_nodes: {},
blocks: {},
miners: {
"MINER": MinerProcess {
name: "MINER",
base_node_name: "BASE1",
wallet_name: "SENDER",
mine_until_height: 100000,
stealth: false,
},
},
ffi_wallets: {
"FFI_WALLET": WalletFFI {
name: "FFI_WALLET",
port: 18010,
wallet: Mutex {
data: Wallet {
ptr: 0x00005613320a0690,
liveness_data: Mutex {
data: {
"da0fae7c96b1ea31ebecda7eece068a9926f9cc88794e65e7ab6d122e2825700fa": ContactsLivenessData {
ptr: 0x00007fb69405f300,
},
},
poisoned: false,
..
},
balance: CachedBalance {
available: 0,
time_locked: 0,
pending_incoming: 0,
pending_outgoing: 0,
},
},
poisoned: false,
..
},
},
},
wallets: {},
merge_mining_proxies: {},
chat_clients: [],
transactions: {},
wallet_addresses: {},
utxos: {},
output_hash: None,
pre_image: None,
wallet_connected_to_base_node: {
"SENDER": "BASE1",
"RECEIVER": "BASE1",
},
seed_nodes: [
"SEED",
],
wallet_tx_ids: {},
errors: [],
last_imported_tx_ids: [],
last_merge_miner_response: Null,
}
github-actions / Test Results (Integration tests)
All 3 runs failed: Scenario: As a client I want to send a one-sided transaction: tests/features/WalletFFI.feature:175:5
artifacts/junit-ffi-cucumber/cucumber-output-junit.xml [took 8m 36s]
Raw output
Step panicked. Captured output: Transaction from SENDER to FFI_WALLET with amount 2400000 at fee 5 failed to be broadcasted
Scenario: As a client I want to send a one-sided transaction
✔ Given I have a seed node SEED
✔ When I have a base node BASE1 connected to all seed nodes
✔ When I have wallet SENDER connected to base node BASE1
✔ And I have a ffi wallet FFI_WALLET connected to base node SEED
✔ When I have wallet RECEIVER connected to base node BASE1
✔ When I add contact with alias ALIAS1 and address of SENDER to ffi wallet FFI_WALLET
✔ When I add contact with alias ALIAS2 and address of RECEIVER to ffi wallet FFI_WALLET
✔ When I have mining node MINER connected to base node BASE1 and wallet SENDER
✔ When mining node MINER mines 10 blocks
✔ Then all nodes are at height 10
✔ Then I wait for wallet SENDER to have at least 129239250000 uT
✘ And I send 2400000 uT from wallet SENDER to wallet FFI_WALLET at fee 5
Step failed:
Defined: tests/features/WalletFFI.feature:191:9
Matched: integration_tests/tests/steps/wallet_steps.rs:839:1
Step panicked. Captured output: Transaction from SENDER to FFI_WALLET with amount 2400000 at fee 5 failed to be broadcasted
Client {
base_nodes: {},
blocks: {},
miners: {
"MINER": MinerProcess {
name: "MINER",
base_node_name: "BASE1",
wallet_name: "SENDER",
mine_until_height: 100000,
stealth: false,
},
},
ffi_wallets: {
"FFI_WALLET": WalletFFI {
name: "FFI_WALLET",
port: 18210,
wallet: Mutex {
data: Wallet {
ptr: 0x0000561331a46080,
liveness_data: Mutex {
data: {
"400fd313f8dedbddec025332689bfe43d3f7a314f740cfb59988a0433c15a92dfa": ContactsLivenessData {
ptr: 0x00007fb5480202c0,
},
},
poisoned: false,
..
},
balance: CachedBalance {
available: 0,
time_locked: 0,
pending_incoming: 0,
pending_outgoing: 0,
},
},
poisoned: false,
..
},
},
},
wallets: {},
merge_mining_proxies: {},
chat_clients: [],
transactions: {},
wallet_addresses: {},
utxos: {},
output_hash: None,
pre_image: None,
wallet_connected_to_base_node: {
"SENDER": "BASE1",
"RECEIVER": "BASE1",
},
seed_nodes: [
"SEED",
],
wallet_tx_ids: {},
errors: [],
last_imported_tx_ids: [],
last_merge_miner_response: Null,
}
github-actions / Test Results (Integration tests)
All 3 runs failed: Scenario: As a client I want to receive a one-sided transaction: tests/features/WalletFFI.feature:212:5
artifacts/junit-ffi-cucumber/cucumber-output-junit.xml [took 2m 24s]
Raw output
Step panicked. Captured output: base nodes not successfully synchronized at height 12, {"SEED": 12, "BASE1": 12, "BASE2": 0}
Scenario: As a client I want to receive a one-sided transaction
✔ Given I have a seed node SEED
✔ When I have a base node BASE1 connected to all seed nodes
✔ When I have a base node BASE2 connected to all seed nodes
✔ When I have wallet SENDER connected to base node BASE1
✔ And I have a ffi wallet FFI_RECEIVER connected to base node BASE2
✔ When I have mining node MINER connected to base node BASE1 and wallet SENDER
✔ When mining node MINER mines 10 blocks
✔ Then I wait for wallet SENDER to have at least 5000000 uT
✔ Then I send a one-sided transaction of 1000000 uT from SENDER to FFI_RECEIVER at fee 20
✔ When mining node MINER mines 2 blocks
✘ Then all nodes are at height 12
Step failed:
Defined: tests/features/WalletFFI.feature:223:9
Matched: integration_tests/tests/steps/node_steps.rs:166:1
Step panicked. Captured output: base nodes not successfully synchronized at height 12, {"SEED": 12, "BASE1": 12, "BASE2": 0}
Client {
base_nodes: {},
blocks: {},
miners: {
"MINER": MinerProcess {
name: "MINER",
base_node_name: "BASE1",
wallet_name: "SENDER",
mine_until_height: 100000,
stealth: false,
},
},
ffi_wallets: {
"FFI_RECEIVER": WalletFFI {
name: "FFI_RECEIVER",
port: 18297,
wallet: Mutex {
data: Wallet {
ptr: 0x00005613320a0690,
liveness_data: Mutex {
data: {},
poisoned: false,
..
},
balance: CachedBalance {
available: 0,
time_locked: 0,
pending_incoming: 0,
pending_outgoing: 0,
},
},
poisoned: false,
..
},
},
},
wallets: {},
merge_mining_proxies: {},
chat_clients: [],
transactions: {},
wallet_addresses: {},
utxos: {},
output_hash: None,
pre_image: None,
wallet_connected_to_base_node: {
"SENDER": "BASE1",
},
seed_nodes: [
"SEED",
],
wallet_tx_ids: {
"c26f1ddba08c916b2598ddc2572b75b7cd7a88d66829e93c13d19c9d2019634f3e": [
11648538624338458452,
],
"d0413955ac720ca775ab1f0d59b91682616cfbb234e45490fef6e9086987f1741e": [
11648538624338458452,
],
},
errors: [],
last_imported_tx_ids: [],
last_merge_miner_response: Null,
}
github-actions / Test Results (Integration tests)
All 3 runs failed: Scenario: Simple Merge Mining: tests/features/MergeMining.feature:35:3
artifacts/junit-cucumber/cucumber-output-junit.xml [took 7s]
Raw output
Step panicked. Captured output: called `Result::unwrap()` on an `Err` value: reqwest::Error { kind: Request, url: Url { scheme: "http", cannot_be_a_base: false, username: "", password: None, host: Some(Ipv4(127.0.0.1)), port: Some(18466), path: "/json_rpc", query: None, fragment: None }, source: hyper::Error(Connect, ConnectError("tcp connect error", Os { code: 111, kind: ConnectionRefused, message: "Connection refused" })) }
Scenario: Simple Merge Mining
✔ Given I have a seed node NODE
✔ When I have wallet WALLET connected to all seed nodes
✔ And I have a merge mining proxy PROXY connected to NODE and WALLET with default config
✘ When I merge mine 2 blocks via PROXY
Step failed:
Defined: tests/features/MergeMining.feature:39:5
Matched: integration_tests/tests/steps/merge_mining_steps.rs:139:1
Step panicked. Captured output: called `Result::unwrap()` on an `Err` value: reqwest::Error { kind: Request, url: Url { scheme: "http", cannot_be_a_base: false, username: "", password: None, host: Some(Ipv4(127.0.0.1)), port: Some(18466), path: "/json_rpc", query: None, fragment: None }, source: hyper::Error(Connect, ConnectError("tcp connect error", Os { code: 111, kind: ConnectionRefused, message: "Connection refused" })) }
Client {
base_nodes: {},
blocks: {},
miners: {},
ffi_wallets: {},
wallets: {},
merge_mining_proxies: {
"PROXY": MergeMiningProxyProcess {
name: "PROXY",
base_node_name: "NODE",
wallet_name: "WALLET",
port: 18466,
origin_submission: true,
id: 1,
stealth: false,
},
},
chat_clients: [],
transactions: {},
wallet_addresses: {},
utxos: {},
output_hash: None,
pre_image: None,
wallet_connected_to_base_node: {
"WALLET": "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: Sync burned output: tests/features/Sync.feature:34:3
artifacts/junit-cucumber/cucumber-output-junit.xml [took 11s]
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: Sync burned output
✔ Given I have a seed node NODE
✔ When I have a base node NODE1 connected to all seed nodes
✔ 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 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
Step failed:
Defined: tests/features/Sync.feature:41: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: "NODE",
wallet_name: "WALLET_A",
mine_until_height: 100000,
stealth: false,
},
},
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",
},
seed_nodes: [
"NODE",
],
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)
32 tests found
There are 32 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: Reply to message: tests/features/ChatFFI.feature:68:3
Scenario: Simple Merge Mining: tests/features/MergeMining.feature:35: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