GitHub Actions / Test Results (Integration tests)
failed
May 5, 2025 in 0s
5 fail, 31 pass in 1h 15m 35s
Annotations
github-actions / Test Results (Integration tests)
1 out of 2 runs failed: Scenario: A message is propagated between side loaded chat and client via 3rd party: tests/features/ChatFFI.feature:105:3
artifacts/junit-ffi-cucumber/cucumber-output-junit.xml [took 2m 1s]
Raw output
Step panicked. Captured output: Receiver \U0001f339\U0001f30a\U0001f48b\U0001f315\U0001f43c\U0001f69c\U0001f3bc\U0001f375\U0001f378\U0001f34d\U0001f69a\U0001f981\U0001f3b9\U0001f489\U0001f4a4\U0001f4f1\U0001f409\U0001f344\U0001f40c\U0001f34c\U0001f33d\U0001f608\U0001f34a\U0001f41b\U0001f3b7\U0001f692\U0001f60d\U0001f981\U0001f34e\U0001f986\U0001f330\U0001f69c\U0001f69c\U0001f319\U0001f44d⏰\U0001f60e\U0001f36c\U0001f437\U0001f526\U0001f3b9\U0001f36f\U0001f389\U0001f3bb\U0001f6b0\U0001f366\U0001f423\U0001f680\U0001f3bd\U0001f357⭐\U0001f60e\U0001f489\U0001f411\U0001f3ac\U0001f43b\U0001f389\U0001f6bd\U0001f3e0\U0001f528\U0001f681\U0001f490\U0001f375\U0001f3bd\U0001f3a2\U0001f3b8\U0001f4a8 only received 0/1 messages
Scenario: A message is propagated between side loaded chat and client via 3rd party
✔ Given I have a seed node SEED_A
✔ Given I have a ffi wallet WALLET_A connected to base node SEED_A
✔ When I have a sideloaded chat FFI client CHAT_A from WALLET_A
✔ When I have a chat FFI client CHAT_B connected to seed node SEED_A
✔ When I use CHAT_A to send a message 'Hey there' to CHAT_B
✘ Then CHAT_B will have 1 message with CHAT_A
Step failed:
Defined: tests/features/ChatFFI.feature:111:5
Matched: integration_tests/tests/steps/chat_steps.rs:126:1
Step panicked. Captured output: Receiver \U0001f339\U0001f30a\U0001f48b\U0001f315\U0001f43c\U0001f69c\U0001f3bc\U0001f375\U0001f378\U0001f34d\U0001f69a\U0001f981\U0001f3b9\U0001f489\U0001f4a4\U0001f4f1\U0001f409\U0001f344\U0001f40c\U0001f34c\U0001f33d\U0001f608\U0001f34a\U0001f41b\U0001f3b7\U0001f692\U0001f60d\U0001f981\U0001f34e\U0001f986\U0001f330\U0001f69c\U0001f69c\U0001f319\U0001f44d⏰\U0001f60e\U0001f36c\U0001f437\U0001f526\U0001f3b9\U0001f36f\U0001f389\U0001f3bb\U0001f6b0\U0001f366\U0001f423\U0001f680\U0001f3bd\U0001f357⭐\U0001f60e\U0001f489\U0001f411\U0001f3ac\U0001f43b\U0001f389\U0001f6bd\U0001f3e0\U0001f528\U0001f681\U0001f490\U0001f375\U0001f3bd\U0001f3a2\U0001f3b8\U0001f4a8 only received 0/1 messages
Client {
base_nodes: {},
blocks: {},
miners: {},
ffi_wallets: {
"WALLET_A": WalletFFI {
name: "WALLET_A",
port: 18088,
base_dir: "/runner/_work/tari/tari/integration_tests/tests/temp/cucumber_57030/Chat FFI messaging/A message is propagated between side loaded chat and client via 3rd party/ffi_wallets/WALLET_A_port_18088",
wallet: Mutex {
data: Wallet {
ptr: 0x000059d982e7c780,
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: {},
seed_nodes: [
"SEED_A",
],
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 client I want to receive a one-sided transaction: tests/features/WalletFFI.feature:212:5
artifacts/junit-ffi-cucumber/cucumber-output-junit.xml [took 11m 1s]
Raw output
Step panicked. Captured output: Counter not adequate! Counter is 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
✘ Then ffi wallet FFI_RECEIVER detects AT_LEAST 1 ffi transactions to be TRANSACTION_STATUS_ONE_SIDED_UNCONFIRMED
Step failed:
Defined: tests/features/WalletFFI.feature:224:9
Matched: integration_tests/tests/steps/wallet_ffi_steps.rs:453:1
Step panicked. Captured output: Counter not adequate! Counter is 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: 18093,
base_dir: "/runner/_work/tari/tari/integration_tests/tests/temp/cucumber_57030/Wallet FFI/As a client I want to receive a one-sided transaction/ffi_wallets/FFI_RECEIVER_port_18093",
wallet: Mutex {
data: Wallet {
ptr: 0x000059d9829de3b0,
liveness_data: Mutex {
data: {},
poisoned: false,
..
},
balance: CachedBalance {
available: 0,
time_locked: 0,
pending_incoming: 1000000,
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: {
"H4Akh8fAhRJ5pJpbEWANqPXyffbU75wXyb6WL4UtXyRL4uA46YYde9FhzVr511NKZiDJFnpcyfUZSHCwDgkjh7nbGHP": [
4009756325137314289,
],
"H4AYQ9gdcxMPCarwA2LZxruTJh1ULsneuHuVMZVuGaxmdatmukvmf5MoeYc4LdXdGQdqVk2e3SVqPUWocFAkh3eHUs1": [
4009756325137314289,
],
},
errors: [],
last_imported_tx_ids: [],
last_merge_miner_response: Null,
}
github-actions / Test Results (Integration tests)
All 3 runs failed: Scenario: Simple reorg to stronger chain: tests/features/Reorgs.feature:8:3
artifacts/junit-cucumber/cucumber-output-junit.xml [took 2m 20s]
Raw output
Step panicked. Captured output: base node didn't synchronize successfully with height 10, current chain height 3
Scenario: Simple reorg to stronger chain
✔ 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 3 blocks with min difficulty 1 and max difficulty 50
✔ Given I have a seed node SEED_C
✔ When I have a base node C connected to seed SEED_C
✔ When I have wallet WC connected to base node C
✔ When I have mining node CM connected to base node C and wallet WC
✔ When mining node CM mines 10 blocks with min difficulty 51 and max difficulty 9999999999
✔ Then node B is at height 3
✔ Then node C is at height 10
✔ When I have a base node SA connected to nodes B,C
✘ Then node SA is at height 10
Step failed:
Defined: tests/features/Reorgs.feature:27:5
Matched: integration_tests/tests/steps/node_steps.rs:218:1
Step panicked. Captured output: base node didn't synchronize successfully with height 10, current chain height 3
Client {
base_nodes: {},
blocks: {},
miners: {
"BM": MinerProcess {
name: "BM",
base_node_name: "B",
wallet_name: "WB",
mine_until_height: 100000,
stealth: false,
},
"CM": MinerProcess {
name: "CM",
base_node_name: "C",
wallet_name: "WC",
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",
"WC": "C",
},
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)
All 3 runs failed: Scenario: Simple reorg with burned output: tests/features/Reorgs.feature:33:3
artifacts/junit-cucumber/cucumber-output-junit.xml [took 4m 3s]
Raw output
Step panicked. Captured output: base node didn't synchronize successfully with height 17, current chain height 15
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
✔ When I have a base node C connected to seed SEED_C
✔ When I have wallet WC connected to base node C
✔ When I have mining node CM connected to base node C and wallet WC
✔ When mining node CM mines 17 blocks with min difficulty 1 and max difficulty 1
✔ Then node B is at height 15
✔ Then node C is at height 17
✔ When I have a base node SA connected to nodes B,C
✘ Then node SA is at height 17
Step failed:
Defined: tests/features/Reorgs.feature:58:5
Matched: integration_tests/tests/steps/node_steps.rs:218:1
Step panicked. Captured output: base node didn't synchronize successfully with height 17, current chain height 15
Client {
base_nodes: {},
blocks: {},
miners: {
"BM": MinerProcess {
name: "BM",
base_node_name: "B",
wallet_name: "WB",
mine_until_height: 100000,
stealth: false,
},
"CM": MinerProcess {
name: "CM",
base_node_name: "C",
wallet_name: "WC",
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",
"WC": "C",
},
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)
All 3 runs failed: Scenario: When a new node joins the network, it receives all peers: tests/features/Sync.feature:77:3
artifacts/junit-cucumber/cucumber-output-junit.xml [took 2m 36s]
Raw output
Step panicked. Captured output: Peer was not connected in time, connected to 8 peers
Scenario: When a new node joins the network, it receives all peers
✔ Given I have 10 seed nodes
✔ When I have a base node NODE1 connected to all seed nodes
✘ When I wait for NODE1 to have 10 connections
Step failed:
Defined: tests/features/Sync.feature:80:5
Matched: integration_tests/tests/steps/node_steps.rs:122:1
Step panicked. Captured output: Peer was not connected in time, connected to 8 peers
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",
"seed_node_1",
"seed_node_2",
"seed_node_3",
"seed_node_4",
"seed_node_5",
"seed_node_6",
"seed_node_7",
"seed_node_8",
"seed_node_9",
],
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)
36 tests found
There are 36 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:105:3
Scenario: A message is sent directly between two FFI clients: tests/features/ChatFFI.feature:49:3
Scenario: A message receives a delivery receipt via FFI: tests/features/ChatFFI.feature:74:3
Scenario: A message receives a read receipt via FFI: tests/features/ChatFFI.feature:82:3
Scenario: A single message is fetched from FFI: tests/features/ChatFFI.feature:113: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: Callback for status change is received: tests/features/ChatFFI.feature:41:3
Scenario: Chat shuts down without any errors: tests/features/ChatFFI.feature:59:3
Scenario: Clear out mempool: tests/features/Mempool.feature:46:3
Scenario: Create burn transaction: tests/features/WalletTransactions.feature:412:3
Scenario: Fetches all addresses from FFI conversations: tests/features/ChatFFI.feature:91:3
Scenario: Node rolls back reorg on invalid block: tests/features/Reorgs.feature:63:3
Scenario: Reply to message: tests/features/ChatFFI.feature:64: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: 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: Verify gprc can create block with more than 1 coinbase: tests/features/BlockTemplate.feature:14:5
Scenario: Wallet imports pre_mine UTXO: tests/features/WalletTransactions.feature:170:3
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