1 parse errors, 4 fail, 13 skipped, 1 pass in 27m 39s
Annotations
Check failure on line 0 in artifacts/junit-cucumber/cucumber-output-junit.xml
github-actions / Test Results (Integration tests)
Error processing result file
CData section too big found, line 197664, column 2 (cucumber-output-junit.xml, line 197664)
Raw output
artifacts/junit-cucumber/cucumber-output-junit.xml
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 30s]
Raw output
Step panicked. Captured output: called `Result::unwrap()` on an `Err` value: Status { code: NotFound, message: "Transaction not found", metadata: MetadataMap { headers: {"content-type": "application/grpc", "date": "Wed, 28 May 2025 15:51:47 GMT"} }, source: None }
Scenario: As a client I want to receive contact liveness events
✔ Given I have a seed node SEED
✔ And I have non-default wallet WALLET1 connected to all seed nodes using DirectOnly
✔ And I have non-default wallet WALLET2 connected to all seed nodes using DirectOnly
✔ And I have a ffi wallet FFI_WALLET connected to seed node SEED
✔ When I add contact with alias ALIAS1 and address of WALLET1 to ffi wallet FFI_WALLET
✔ And I add contact with alias ALIAS2 and address of WALLET2 to ffi wallet FFI_WALLET
✔ And I have mining node MINER1 connected to base node SEED and wallet WALLET1
✔ And I have mining node MINER2 connected to base node SEED and wallet WALLET2
✔ And mining node MINER1 mines 1 blocks
✔ And mining node MINER2 mines 5 blocks
✔ Then I wait for wallet WALLET1 to have at least 100000000 uT
✔ And I wait for wallet WALLET2 to have at least 100000000 uT
✘ When I send 100000000 uT without waiting for broadcast from wallet WALLET1 to wallet FFI_WALLET at fee 20
Step failed:
Defined: tests/features/WalletFFI.feature:89:9
Matched: integration_tests/tests/steps/wallet_steps.rs:701:1
Step panicked. Captured output: called `Result::unwrap()` on an `Err` value: Status { code: NotFound, message: "Transaction not found", metadata: MetadataMap { headers: {"content-type": "application/grpc", "date": "Wed, 28 May 2025 15:51:47 GMT"} }, source: None }
Client {
base_nodes: {},
blocks: {},
miners: {
"MINER1": MinerProcess {
name: "MINER1",
base_node_name: "SEED",
wallet_name: "WALLET1",
mine_until_height: 100000,
stealth: false,
},
"MINER2": MinerProcess {
name: "MINER2",
base_node_name: "SEED",
wallet_name: "WALLET2",
mine_until_height: 100000,
stealth: false,
},
},
ffi_wallets: {
"FFI_WALLET": WalletFFI {
name: "FFI_WALLET",
port: 18068,
base_dir: "/runner/_work/tari/tari/integration_tests/tests/temp/cucumber_57169/Wallet FFI/As a client I want to receive contact liveness events/ffi_wallets/FFI_WALLET_port_18068",
wallet: Mutex {
data: Wallet {
ptr: 0x00005dde8fd01790,
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: {},
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)
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 1m 16s]
Raw output
Step panicked. Captured output: called `Result::unwrap()` on an `Err` value: Status { code: NotFound, message: "Transaction not found", metadata: MetadataMap { headers: {"content-type": "application/grpc", "date": "Wed, 28 May 2025 15:54:04 GMT"} }, source: None }
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:870:1
Step panicked. Captured output: called `Result::unwrap()` on an `Err` value: Status { code: NotFound, message: "Transaction not found", metadata: MetadataMap { headers: {"content-type": "application/grpc", "date": "Wed, 28 May 2025 15:54:04 GMT"} }, source: None }
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: 18327,
base_dir: "/runner/_work/tari/tari/integration_tests/tests/temp/cucumber_57169/Wallet FFI/As a client I want to retrieve a list of transactions I have made and received/ffi_wallets/FFI_WALLET_port_18327",
wallet: Mutex {
data: Wallet {
ptr: 0x00005dde8f6def30,
liveness_data: Mutex {
data: {
"H4G2rPToysWq8Xs9nUSC52wcjSgBjgwxxqEJuVgYgXyRtQtFhKRHZYkvrDTfYLQFL1vxoPaCiPmyRtpsmhbM3gcd6bK": ContactsLivenessData {
ptr: 0x00007b3d1004cc20,
},
},
poisoned: false,
..
},
balance: CachedBalance {
available: 0,
time_locked: 0,
pending_incoming: 0,
pending_outgoing: 0,
},
},
poisoned: false,
..
},
},
},
wallets: {},
merge_mining_proxies: {},
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 1m 17s]
Raw output
Step panicked. Captured output: called `Result::unwrap()` on an `Err` value: Status { code: NotFound, message: "Transaction not found", metadata: MetadataMap { headers: {"content-type": "application/grpc", "date": "Wed, 28 May 2025 16:00:53 GMT"} }, source: None }
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 BASE1
✔ 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:870:1
Step panicked. Captured output: called `Result::unwrap()` on an `Err` value: Status { code: NotFound, message: "Transaction not found", metadata: MetadataMap { headers: {"content-type": "application/grpc", "date": "Wed, 28 May 2025 16:00:53 GMT"} }, source: None }
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: 18434,
base_dir: "/runner/_work/tari/tari/integration_tests/tests/temp/cucumber_57169/Wallet FFI/As a client I want to send a one-sided transaction/ffi_wallets/FFI_WALLET_port_18434",
wallet: Mutex {
data: Wallet {
ptr: 0x00005dde8fe5d9d0,
liveness_data: Mutex {
data: {
"H4MA5DxZfVszB297qJdQvCh5BU5BRgzDzgW5mc16M3Rvd5Do7HobQfsjaauqnxhnHdNuV7Pdt33UTnVLoXEYeM7221i": ContactsLivenessData {
ptr: 0x00007b3bc8071ab0,
},
"H4NXCxHH6DQ3zPNzArzLVkpG3BEK78omSD5zTqLshzhmBBNCoiC5Cxqa6bpWk5hniuoGMMdAMjJwvVfJuGXYRHGgMv": ContactsLivenessData {
ptr: 0x00007b40bc020fd0,
},
},
poisoned: false,
..
},
balance: CachedBalance {
available: 0,
time_locked: 0,
pending_incoming: 0,
pending_outgoing: 0,
},
},
poisoned: false,
..
},
},
},
wallets: {},
merge_mining_proxies: {},
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 51s]
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: 18017,
base_dir: "/runner/_work/tari/tari/integration_tests/tests/temp/cucumber_57169/Wallet FFI/As a client I want to receive a one-sided transaction/ffi_wallets/FFI_RECEIVER_port_18017",
wallet: Mutex {
data: Wallet {
ptr: 0x00005dde901ce520,
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: {},
transactions: {},
wallet_addresses: {},
utxos: {},
output_hash: None,
pre_image: None,
wallet_connected_to_base_node: {
"SENDER": "BASE1",
},
seed_nodes: [
"SEED",
],
wallet_tx_ids: {
"H48Sn8zZ2GFPtcB5x4bFvZ1PivSHJswb57ArtQ8BMWkNSfTjRvzbFqRVxqKKoFgxCY8738r9tK87QW5K5sHVXzXtJn5": [
16489999020104207956,
],
"H4GZKjRei1FCqZwgTWQEpniQfa2S1HjRtVtayCYmhq3E4aVovhfNhaAJSdMGyvGtUA9wnHbXC8EjUnQCfPY2RJYwY1D": [
16489999020104207956,
],
},
errors: [],
last_imported_tx_ids: [],
last_merge_miner_response: Null,
}
Check notice on line 0 in .github
github-actions / Test Results (Integration tests)
13 skipped tests found
There are 13 skipped tests, see "Raw output" for the full list of skipped 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: 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: Fetches all addresses from FFI conversations: tests/features/ChatFFI.feature:91:3
Scenario: Reply to message: tests/features/ChatFFI.feature:64:3
Check notice on line 0 in .github
github-actions / Test Results (Integration tests)
18 tests found
There are 18 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: 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: Fetches all addresses from FFI conversations: tests/features/ChatFFI.feature:91:3
Scenario: Reply to message: tests/features/ChatFFI.feature:64:3