chore: merging dev into feat-libp2p #667
GitHub Actions / Test Results (Integration tests)
failed
Nov 28, 2024 in 0s
2 fail, 22 pass in 19m 11s
Annotations
github-actions / Test Results (Integration tests)
2 out of 3 runs failed: Scenario: As a client I want to retrieve a list of transactions I have made and received: tests/features/WalletFFI.feature:101:5
artifacts/junit-ffi-cucumber/cucumber-output-junit.xml [took 2m 15s]
Raw output
Step panicked. Captured output: FFI_WALLET doesn't have at least 2 contacts with status Online!
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
✔ When I have wallet RECEIVER connected to base node BASE1
✔ And I have a ffi wallet FFI_WALLET connected to base node BASE1
✔ When I add contact with alias ALIAS_SENDER and address of SENDER to ffi wallet FFI_WALLET
✔ When I add contact with alias ALIAS_RECEIVER and address of RECEIVER to ffi wallet FFI_WALLET
✔ When I add contact with alias ALIAS_FFI_WALLET and address of FFI_WALLET to wallet SENDER
✔ When I add contact with alias ALIAS_FFI_WALLET and address of FFI_WALLET to wallet RECEIVER
✔ When I add contact with alias ALIAS_RECEIVER and address of RECEIVER to wallet SENDER
✔ When I add contact with alias ALIAS_SENDER and address of SENDER to wallet RECEIVER
✘ Then I wait for ffi wallet FFI_WALLET to have at least 2 contacts to be Online
Step failed:
Defined: tests/features/WalletFFI.feature:114:9
Matched: integration_tests/tests/steps/wallet_ffi_steps.rs:261:1
Step panicked. Captured output: FFI_WALLET doesn't have at least 2 contacts with status Online!
Client {
base_nodes: {},
blocks: {},
miners: {},
ffi_wallets: {
"FFI_WALLET": WalletFFI {
name: "FFI_WALLET",
tcp_port: 18101,
udp_port: 18162,
base_dir: "/runner/_work/tari/tari/integration_tests/tests/temp/cucumber_67829/Wallet FFI/As a client I want to retrieve a list of transactions I have made and received/ffi_wallets/FFI_WALLET_port_18101",
wallet: Mutex {
data: Wallet {
ptr: 0x0000564d20466370,
liveness_data: Mutex {
data: {
"H43VptmsfjvegtCkVinc2Ey245zRVrsLMSH6ja1LB5Q5XgfCBF1aj5yddhHJUFRF6TeF9oMndsdtJDGtFJdZ5YcwCcm": ContactsLivenessData {
ptr: 0x00007fe2f0002d00,
},
"H4ARnjtAfvNgjz6aLHKwtkGveEPZnvqJ6PJTQ8TG4sjTP8zgRMReQMg6jtGX7L8HkLhNZSc9J3Qt7pzYfZQZp5ssTBF": ContactsLivenessData {
ptr: 0x00007fe28c0033f0,
},
},
poisoned: false,
..
},
balance: CachedBalance {
available: 0,
time_locked: 0,
pending_incoming: 0,
pending_outgoing: 0,
},
},
poisoned: false,
..
},
},
},
wallets: {},
merge_mining_proxies: {},
transactions: {},
stopped_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)
2 out of 3 runs failed: Scenario: Transactions are propagated through a network: tests/features/Mempool.feature:8:3
artifacts/junit-cucumber/cucumber-output-junit.xml [took 1m 1s]
Raw output
Step panicked. Captured output: Service 'Tcp' on port '18097' never started for 'Node_1'
Scenario: Transactions are propagated through a network
✔ Given I have 8 seed nodes
✔ When I have a base node SENDER connected to all seed nodes
✘ When I have 8 base nodes connected to all seed nodes
Step failed:
Defined: tests/features/Mempool.feature:15:5
Matched: integration_tests/tests/steps/node_steps.rs:79:1
Step panicked. Captured output: Service 'Tcp' on port '18097' never started for 'Node_1'
Client {
base_nodes: {},
blocks: {},
miners: {},
ffi_wallets: {},
wallets: {},
merge_mining_proxies: {},
transactions: {},
stopped_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",
],
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)
24 tests found
There are 24 tests, see "Raw output" for the full list of tests.
Raw output
Scenario: As a client I want to be able to restore my ffi wallet from seed words: tests/features/WalletFFI.feature:14:5
Scenario: As a client I want to receive a one-sided transaction: tests/features/WalletFFI.feature:239:5
Scenario: As a client I want to receive contact liveness events: tests/features/WalletFFI.feature:86:5
Scenario: As a client I want to retrieve a list of transactions I have made and received: tests/features/WalletFFI.feature:101:5
Scenario: As a client I want to retrieve the mnemonic word list for a given language: tests/features/WalletFFI.feature:25:5
Scenario: As a client I want to send a one-sided transaction: tests/features/WalletFFI.feature:204: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: Clear out mempool: tests/features/Mempool.feature:44:3
Scenario: Create burn transaction: tests/features/WalletTransactions.feature:412:3
Scenario: Node rolls back reorg on invalid block: tests/features/Reorgs.feature:63: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:122:3
Loading