11 fail, 21 pass in 34m 56s
Annotations
github-actions / Test Results (Integration tests)
All 3 runs failed: Scenario: Verify UTXO and kernel MMR size in header: tests/features/BlockTemplate.feature:8:1
artifacts/junit-cucumber/cucumber-output-junit.xml [took 10s]
Raw output
Step panicked. Captured output: Service on port 18359 never started
Scenario: Verify UTXO and kernel MMR size in header
✘ Given I have a seed node SEED_A
Step failed:
Defined: tests/features/BlockTemplate.feature:9:5
Matched: integration_tests/tests/steps/node_steps.rs:42:1
Step panicked. Captured output: Service on port 18359 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",
],
wallet_tx_ids: {},
errors: [],
last_imported_tx_ids: [],
last_merge_miner_response: Null,
}
github-actions / Test Results (Integration tests)
All 3 runs failed: Scenario: Transactions are propagated through a network: tests/features/Mempool.feature:8:3
artifacts/junit-cucumber/cucumber-output-junit.xml [took 10s]
Raw output
Step panicked. Captured output: Service on port 18338 never started
Scenario: Transactions are propagated through a network
✘ Given I have 8 seed nodes
Step failed:
Defined: tests/features/Mempool.feature:13:5
Matched: integration_tests/tests/steps/node_steps.rs:261:1
Step panicked. Captured output: Service on port 18338 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_node_0",
],
wallet_tx_ids: {},
errors: [],
last_imported_tx_ids: [],
last_merge_miner_response: Null,
}
github-actions / Test Results (Integration tests)
All 3 runs failed: Scenario: Clear out mempool: tests/features/Mempool.feature:46:3
artifacts/junit-cucumber/cucumber-output-junit.xml [took 10s]
Raw output
Step panicked. Captured output: Service on port 18359 never started
Scenario: Clear out mempool
✘ Given I have 1 seed nodes
Step failed:
Defined: tests/features/Mempool.feature:47:5
Matched: integration_tests/tests/steps/node_steps.rs:261:1
Step panicked. Captured output: Service on port 18359 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_node_0",
],
wallet_tx_ids: {},
errors: [],
last_imported_tx_ids: [],
last_merge_miner_response: Null,
}
github-actions / Test Results (Integration tests)
All 3 runs failed: Scenario: Zero-conf transactions: tests/features/Mempool.feature:124:3
artifacts/junit-cucumber/cucumber-output-junit.xml [took 10s]
Raw output
Step panicked. Captured output: Service on port 18094 never started
Scenario: Zero-conf transactions
✘ Given I have 1 seed nodes
Step failed:
Defined: tests/features/Mempool.feature:125:5
Matched: integration_tests/tests/steps/node_steps.rs:261:1
Step panicked. Captured output: Service on port 18094 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_node_0",
],
wallet_tx_ids: {},
errors: [],
last_imported_tx_ids: [],
last_merge_miner_response: Null,
}
github-actions / Test Results (Integration tests)
All 3 runs failed: Scenario: Simple propagation: tests/features/Propagation.feature:26:3
artifacts/junit-cucumber/cucumber-output-junit.xml [took 10s]
Raw output
Step panicked. Captured output: Service on port 18281 never started
Scenario: Simple propagation
✘ Given I have 2 seed nodes
Step failed:
Defined: tests/features/Propagation.feature:27:5
Matched: integration_tests/tests/steps/node_steps.rs:261:1
Step panicked. Captured output: Service on port 18281 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_node_0",
],
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: Simple reorg with burned output: tests/features/Reorgs.feature:33:3
artifacts/junit-cucumber/cucumber-output-junit.xml [took 1m 11s]
Raw output
Step panicked. Captured output: Service on port 18152 never started
Scenario: Simple reorg with burned output
✔ Given I have a seed node SEED_B
✔ When I have a base node B connected to seed SEED_B
✔ When I have wallet WB connected to base node B
✔ When I have mining node BM connected to base node B and wallet WB
✔ When mining node BM mines 10 blocks with min difficulty 1 and max difficulty 1
✔ When I wait for wallet WB to have at least 55000000000 uT
✔ When I create a burn transaction of 1000000 uT from WB at fee 100
✔ When mining node BM mines 5 blocks with min difficulty 1 and max difficulty 1
✘ Given I have a seed node SEED_C
Step failed:
Defined: tests/features/Reorgs.feature:48:5
Matched: integration_tests/tests/steps/node_steps.rs:42:1
Step panicked. Captured output: Service on port 18152 never started
Client {
base_nodes: {},
blocks: {},
miners: {
"BM": MinerProcess {
name: "BM",
base_node_name: "B",
wallet_name: "WB",
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: {
"WB": "B",
},
seed_nodes: [
"SEED_B",
"SEED_C",
],
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: Syncing node while also mining before tip sync: tests/features/Sync.feature:142:5
artifacts/junit-cucumber/cucumber-output-junit.xml [took 27s]
Raw output
Step panicked. Captured output: Service on port 18024 never started
Scenario Outline: Syncing node while also mining before tip sync
✔ Given I have a seed node SEED
✔ When I have wallet WALLET1 connected to seed node SEED
✔ When I have wallet WALLET2 connected to seed node SEED
✔ When I have mining node MINER connected to base node SEED and wallet WALLET1
✘ When I have a base node SYNCER connected to all seed nodes
Step failed:
Defined: tests/features/Sync.feature:129:5
Matched: integration_tests/tests/steps/node_steps.rs:49:1
Step panicked. Captured output: Service on port 18024 never started
Client {
base_nodes: {},
blocks: {},
miners: {
"MINER": MinerProcess {
name: "MINER",
base_node_name: "SEED",
wallet_name: "WALLET1",
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: {
"WALLET1": "SEED",
"WALLET2": "SEED",
},
seed_nodes: [
"SEED",
],
wallet_tx_ids: {},
errors: [],
last_imported_tx_ids: [],
last_merge_miner_response: Null,
}
github-actions / Test Results (Integration tests)
2 out of 3 runs failed: Scenario: As a wallet I want to submit a transaction: tests/features/WalletQuery.feature:18:3
artifacts/junit-cucumber/cucumber-output-junit.xml [took 10s]
Raw output
Step panicked. Captured output: Service on port 18322 never started
Scenario: As a wallet I want to submit a transaction
✘ Given I have a seed node NODE
Step failed:
Defined: tests/features/WalletQuery.feature:19:5
Matched: integration_tests/tests/steps/node_steps.rs:42:1
Step panicked. Captured output: Service on port 18322 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: [
"NODE",
],
wallet_tx_ids: {},
errors: [],
last_imported_tx_ids: [],
last_merge_miner_response: Null,
}
github-actions / Test Results (Integration tests)
2 out of 3 runs failed: Scenario: Wallet recovery with connected base node staying online: tests/features/WalletRecovery.feature:8:5
artifacts/junit-cucumber/cucumber-output-junit.xml [took 10s]
Raw output
Step panicked. Captured output: Service on port 18360 never started
Scenario: Wallet recovery with connected base node staying online
✘ Given I have a seed node NODE
Step failed:
Defined: tests/features/WalletRecovery.feature:9:7
Matched: integration_tests/tests/steps/node_steps.rs:42:1
Step panicked. Captured output: Service on port 18360 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: [
"NODE",
],
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 contact liveness events: tests/features/WalletFFI.feature:73:5
artifacts/junit-ffi-cucumber/cucumber-output-junit.xml [took 10s]
Raw output
Step panicked. Captured output: Service on port 18267 never started
Scenario: As a client I want to receive contact liveness events
✘ Given I have a seed node SEED
Step failed:
Defined: tests/features/WalletFFI.feature:74:9
Matched: integration_tests/tests/steps/node_steps.rs:42:1
Step panicked. Captured output: Service on port 18267 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",
],
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 client I want to receive a one-sided transaction: tests/features/WalletFFI.feature:212:5
artifacts/junit-ffi-cucumber/cucumber-output-junit.xml [took 14m 43s]
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: 18088,
base_dir: "/runner/_work/tari/tari/integration_tests/tests/temp/cucumber_6420/Wallet FFI/As a client I want to receive a one-sided transaction/ffi_wallets/FFI_RECEIVER_port_18088",
wallet: Mutex {
data: Wallet {
ptr: 0x000055a59d171ad0,
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: {
"aa2f88433b6e05a324bdcb7093a87c0754ef12e838da1a6a52382c396dfae05666": [
10286297852776906142,
],
"960e323815935af0f2fc8547dc06a2db08580f97f0a8e3ff8de5e16e9675794676": [
10286297852776906142,
],
},
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 is propagated between side loaded chat and client via 3rd party: tests/features/ChatFFI.feature:109: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 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