add tests
GitHub Actions / Test Results (Integration tests)
failed
Nov 4, 2023 in 0s
2 fail, 29 pass in 24m 10s
Annotations
github-actions / Test Results (Integration tests)
1 out of 2 runs failed: Scenario: Transactions are propagated through a network: tests/features/Mempool.feature:8:3
artifacts/junit-cucumber/cucumber-output-junit.xml [took 12s]
Raw output
Step panicked. Captured output: called `Result::unwrap()` on an `Err` value: transport error Caused by: 0: error trying to connect: tcp connect error: Connection refused (os error 111) 1: tcp connect error: Connection refused (os error 111) 2: Connection refused (os error 111)
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
✔ When I mine a block on SENDER with coinbase CB1
✔ When I mine 2 blocks on SENDER
✘ Then all nodes are at height 3
Step failed:
Defined: tests/features/Mempool.feature:18:5
Matched: integration_tests/tests/steps/node_steps.rs:166:1
Step panicked. Captured output: called `Result::unwrap()` on an `Err` value: transport error
Caused by:
0: error trying to connect: tcp connect error: Connection refused (os error 111)
1: tcp connect error: Connection refused (os error 111)
2: Connection refused (os error 111)
Client {
base_nodes: {},
blocks: {},
miners: {},
ffi_wallets: {},
wallets: {},
merge_mining_proxies: {},
chat_clients: [],
transactions: {},
wallet_addresses: {},
utxos: {
"CB1": KeyManagerOutput {
version: V0,
value: MicroMinotari(
18462816327,
),
spending_key_id: Managed {
branch: "commitment mask",
index: 1,
},
features: OutputFeatures {
version: V0,
output_type: Coinbase,
maturity: 3,
coinbase_extra: [],
sidechain_feature: None,
range_proof_type: BulletProofPlus,
},
script: TariScript {
script: [
Nop,
],
},
covenant: Covenant {
tokens: [],
},
input_data: ExecutionStack {
items: [
PublicKey(
6ce4506fb1f28ad4fcd2fdaddaa4e0210ce100a8bf209b3b505297d3ec803f18,
),
],
},
script_private_key_id: Managed {
branch: "script key",
index: 1,
},
sender_offset_public_key: 94c8e0e685eac090eed5f4cce0a428107332f8568a52234be5849945f0dd132a,
metadata_signature: CommitmentAndPublicKeySignature {
ephemeral_commitment: HomomorphicCommitment(
c24b45edb2d75cbe56c2d2d650cc8dda025f52343d366119b43682f6d2e73825,
),
ephemeral_pubkey: 4a348692817f87570f321c3d20e69a933ac893794d40641a72c610a49fe02c60,
u_a: RistrettoSecretKey(***),
u_x: RistrettoSecretKey(***),
u_y: RistrettoSecretKey(***),
},
script_lock_height: 0,
encrypted_data: EncryptedData {
data: [
160,
221,
153,
171,
19,
125,
0,
62,
14,
147,
233,
0,
207,
225,
195,
175,
156,
194,
248,
78,
188,
97,
57,
189,
242,
218,
178,
143,
120,
156,
70,
77,
94,
210,
117,
157,
251,
240,
110,
218,
5,
222,
98,
146,
169,
90,
78,
104,
74,
186,
59,
119,
33,
62,
20,
251,
11,
221,
50,
84,
205,
97,
251,
143,
149,
187,
57,
112,
1,
86,
182,
182,
194,
166,
40,
164,
88,
120,
214,
223,
],
},
minimum_value_promise: MicroMinotari(
0,
),
},
},
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,
}
github-actions / Test Results (Integration tests)
1 out of 2 runs failed: Scenario: As a wallet send to a wallet connected to a different base node: tests/features/WalletTransfer.feature:9:3
artifacts/junit-cucumber/cucumber-output-junit.xml [took 9m 11s]
Raw output
Step panicked. Captured output: Wallet WALLET_B failed to have at least 5T, it ended with 0T
Scenario: As a wallet send to a wallet connected to a different base node
✔ Given I have a seed node SEED_A
✔ When I have a seed node SEED_B
✔ When I have a base node NODE_A connected to all seed nodes
✔ When I have a base node NODE_B connected to all seed nodes
✔ When I have wallet WALLET_A with 10T connected to base node NODE_A
✔ When I have wallet WALLET_B connected to base node NODE_B
✔ When I wait 5 seconds
✔ When I transfer 5T from WALLET_A to WALLET_B
✔ When I mine 4 blocks on SEED_A
✔ Then wallet WALLET_A has 5T
✔ When I wait 5 seconds
✘ When wallet WALLET_B has 5T
Step failed:
Defined: tests/features/WalletTransfer.feature:21:5
Matched: integration_tests/tests/steps/wallet_steps.rs:1478:1
Step panicked. Captured output: Wallet WALLET_B failed to have at least 5T, it ended with 0T
Client {
base_nodes: {},
blocks: {},
miners: {
"temp_miner": MinerProcess {
name: "temp_miner",
base_node_name: "NODE_A",
wallet_name: "WALLET_A",
mine_until_height: 100000,
},
},
ffi_wallets: {},
wallets: {},
merge_mining_proxies: {},
chat_clients: [],
transactions: {},
wallet_addresses: {},
utxos: {},
output_hash: None,
pre_image: None,
wallet_connected_to_base_node: {
"WALLET_A": "NODE_A",
"WALLET_B": "NODE_B",
},
seed_nodes: [
"SEED_A",
"SEED_B",
],
wallet_tx_ids: {
"76b7e579fd23d3358464b2d23c352372ce4702a41e80dc1c904b9af56ff04b3aa3": [
7532715896482107407,
],
"a450611f35fe9f351242d48b8dabfd73c9636afd2a7bd0dc020f61efb2655e7aee": [
7532715896482107407,
],
},
errors: [],
last_imported_tx_ids: [],
last_merge_miner_response: Null,
}
Check notice on line 0 in .github
github-actions / Test Results (Integration tests)
31 tests found
There are 31 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 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
Loading