feat: ledger blind sign #6264
Merged
feat: ledger blind sign #6264
GitHub Actions / Test Results (Integration tests)
failed
May 15, 2024 in 0s
3 fail, 30 pass in 40m 9s
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 9s]
Raw output
Step panicked. Captured output: called `Result::unwrap()` on an `Err` value: Status { code: Unimplemented, metadata: MetadataMap { headers: {"date": "Wed, 15 May 2024 22:51:23 GMT", "content-type": "application/grpc", "content-length": "0"} }, source: None }
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:180:1
Step panicked. Captured output: called `Result::unwrap()` on an `Err` value: Status { code: Unimplemented, metadata: MetadataMap { headers: {"date": "Wed, 15 May 2024 22:51:23 GMT", "content-type": "application/grpc", "content-length": "0"} }, source: None }
Client {
base_nodes: {},
blocks: {},
miners: {
"MINER": MinerProcess {
name: "MINER",
base_node_name: "MINER",
wallet_name: "MINER",
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: {},
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)
All 3 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 26s]
Raw output
Step panicked. Captured output: Service on port 18178 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
Step failed:
Defined: tests/features/Sync.feature:126:5
Matched: integration_tests/tests/steps/wallet_steps.rs:146:1
Step panicked. Captured output: Service on port 18178 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: {
"WALLET1": "SEED",
},
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 9m 25s]
Raw output
Step panicked. Captured output: Wallet RECEIVER failed to have at least num 1 txs with status 8, current status is 0
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
✔ And I send 2400000 uT from wallet SENDER to wallet FFI_WALLET at fee 5
✔ Then wallet SENDER has at least 2 transactions that are all TRANSACTION_STATUS_BROADCAST and not cancelled
✔ Then ffi wallet FFI_WALLET detects AT_LEAST 2 ffi transactions to be TRANSACTION_STATUS_BROADCAST
✔ When mining node MINER mines 10 blocks
✔ Then all nodes are at height 20
✔ Then ffi wallet FFI_WALLET detects AT_LEAST 2 ffi transactions to be TRANSACTION_STATUS_MINED
✔ Then I wait for ffi wallet FFI_WALLET to have at least 4000000 uT
✔ And I send 1000000 uT from ffi wallet FFI_WALLET to wallet RECEIVER at fee 5 via one-sided transactions
✔ Then ffi wallet FFI_WALLET detects AT_LEAST 3 ffi transactions to be TRANSACTION_STATUS_BROADCAST
✔ When mining node MINER mines 2 blocks
✔ Then all nodes are at height 22
✘ Then wallet RECEIVER has at least 1 transactions that are all TRANSACTION_STATUS_ONE_SIDED_UNCONFIRMED and not cancelled
Step failed:
Defined: tests/features/WalletFFI.feature:205:9
Matched: integration_tests/tests/steps/wallet_steps.rs:514:1
Step panicked. Captured output: Wallet RECEIVER failed to have at least num 1 txs with status 8, current status 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_WALLET": WalletFFI {
name: "FFI_WALLET",
port: 18238,
base_dir: "/runner/_work/tari/tari/integration_tests/tests/temp/cucumber_48517/Wallet FFI/As a client I want to send a one-sided transaction/ffi_wallets/FFI_WALLET_port_18238",
wallet: Mutex {
data: Wallet {
ptr: 0x00007f7e2c0e4440,
liveness_data: Mutex {
data: {
"38a4d02f01fcab6316defad412fc27488671e28951ca109472c74bba0a48c858cb": ContactsLivenessData {
ptr: 0x00007f7b84113070,
},
"34b75292eeb2cdf90ec01f3cbcee401fb015d4329d6197d17b567fc04cc63a78eb": ContactsLivenessData {
ptr: 0x00007f79fc06ad70,
},
},
poisoned: false,
..
},
balance: CachedBalance {
available: 2400000,
time_locked: 0,
pending_incoming: 1399330,
pending_outgoing: 2400000,
},
},
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: {
"38a4d02f01fcab6316defad412fc27488671e28951ca109472c74bba0a48c858cb": [
9873300639595166508,
16694890294003416219,
],
"dc3c88213b35fbfd0ac0bf07b32fcd9c9efbfa344adada95f05241fdb9b35d2cec": [
9873300639595166508,
16694890294003416219,
],
},
errors: [],
last_imported_tx_ids: [],
last_merge_miner_response: Null,
}
Check notice on line 0 in .github
github-actions / Test Results (Integration tests)
33 tests found
There are 33 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: Verify gprc cna create block with more than 1 coinbase: tests/features/BlockTemplate.feature:14:5
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