review comments
GitHub Actions / Test Results (Integration tests)
failed
Oct 16, 2024 in 0s
2 fail, 34 pass in 38m 11s
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 14m 17s]
Raw output
Step panicked. Captured output: base nodes not successfully synchronized at height 3, {"seed_node_0": 0, "seed_node_1": 3, "seed_node_2": 3, "seed_node_3": 3, "seed_node_4": 3, "seed_node_5": 3, "seed_node_6": 3, "seed_node_7": 3, "SENDER": 3, "Node_0": 3, "Node_1": 3, "Node_2": 3, "Node_3": 3, "Node_4": 3, "Node_5": 3, "Node_6": 3, "Node_7": 3}
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:180:1
Step panicked. Captured output: base nodes not successfully synchronized at height 3, {"seed_node_0": 0, "seed_node_1": 3, "seed_node_2": 3, "seed_node_3": 3, "seed_node_4": 3, "seed_node_5": 3, "seed_node_6": 3, "seed_node_7": 3, "SENDER": 3, "Node_0": 3, "Node_1": 3, "Node_2": 3, "Node_3": 3, "Node_4": 3, "Node_5": 3, "Node_6": 3, "Node_7": 3}
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: Imported {
key: 62220eafacd88319fe411cfc56177647959354a07865a4ebab6fc54e9138430f,
},
features: OutputFeatures {
version: V0,
output_type: Coinbase,
maturity: 3,
coinbase_extra: MaxSizeBytes {
inner: [],
},
sidechain_feature: None,
range_proof_type: BulletProofPlus,
},
script: TariScript {
script: MaxSizeVec {
vec: [
PushPubKey(
7c37157eb9321be2362b7e3b5ec704fd2c240a026915e01d02ad7dba2f4cfb1f,
),
],
_marker: PhantomData<tari_script::op_codes::Opcode>,
},
},
covenant: Covenant {
tokens: MaxSizeVec {
vec: [],
_marker: PhantomData<tari_core::covenants::token::CovenantToken>,
},
},
input_data: ExecutionStack {
items: [],
},
script_private_key_id: Imported {
key: 7c37157eb9321be2362b7e3b5ec704fd2c240a026915e01d02ad7dba2f4cfb1f,
},
sender_offset_public_key: 76ace7caa203e80865f82a1f6dced2f08517251861bb8be221b962864bee463a,
metadata_signature: CommitmentAndPublicKeySignature {
ephemeral_commitment: HomomorphicCommitment(
ae64689b9ca6d11451d8c84797433e90c78f3696387a5752e30b596e08289526,
),
ephemeral_pubkey: f05552ac51fa279d7c083720267e828bab6b4a95d01992922f50537ab6a4403c,
u_a: RistrettoSecretKey(***),
u_x: RistrettoSecretKey(***),
u_y: RistrettoSecretKey(***),
},
script_lock_height: 0,
encrypted_data: EncryptedData {
data: MaxSizeBytes {
inner: [
215,
151,
21,
138,
61,
213,
189,
2,
109,
61,
246,
118,
208,
185,
124,
99,
82,
154,
0,
137,
32,
187,
53,
164,
116,
92,
67,
202,
124,
126,
86,
205,
201,
65,
207,
202,
243,
125,
57,
86,
55,
122,
76,
153,
116,
149,
9,
161,
114,
181,
143,
138,
244,
13,
116,
128,
39,
74,
112,
223,
234,
9,
233,
110,
71,
94,
187,
234,
181,
92,
69,
200,
118,
161,
103,
13,
113,
247,
201,
175,
],
},
},
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: Wallet imports pre_mine UTXO: tests/features/WalletTransactions.feature:170:3
artifacts/junit-cucumber/cucumber-output-junit.xml [took 9m 29s]
Raw output
Step panicked. Captured output: Transaction from WALLET_C to WALLET_A with amount 500000 at fee 100 failed to be broadcasted
Scenario: Wallet imports pre_mine UTXO
✔ Given I have a seed node NODE
✔ When I have 1 base nodes connected to all seed nodes
✔ When I have wallet WALLET_A connected to all seed nodes
✔ When I have wallet WALLET_B connected to all seed nodes
✔ When I have wallet WALLET_C connected to all seed nodes
✔ When I have mining node MINER connected to base node NODE and wallet WALLET_A
✔ When mining node MINER mines 5 blocks
✔ Then all nodes are at height 5
✔ Then I wait for wallet WALLET_A to have at least 10000000000 uT
✔ When I send 1000000 uT from wallet WALLET_A to wallet WALLET_B at fee 100
✔ When mining node MINER mines 6 blocks
✔ Then all nodes are at height 11
✔ Then I wait for wallet WALLET_B to have at least 1000000 uT
✔ Then I stop wallet WALLET_B
✔ When I wait 15 seconds
✔ Then I import WALLET_B unspent outputs as pre_mine outputs to WALLET_C
✔ Then I wait for wallet WALLET_C to have at least 1000000 uT
✘ When I send 500000 uT from wallet WALLET_C to wallet WALLET_A at fee 100
Step failed:
Defined: tests/features/WalletTransactions.feature:188:5
Matched: integration_tests/tests/steps/wallet_steps.rs:849:1
Step panicked. Captured output: Transaction from WALLET_C to WALLET_A with amount 500000 at fee 100 failed to be broadcasted
Client {
base_nodes: {},
blocks: {},
miners: {
"MINER": MinerProcess {
name: "MINER",
base_node_name: "NODE",
wallet_name: "WALLET_A",
mine_until_height: 100000,
stealth: false,
},
},
ffi_wallets: {},
wallets: {},
merge_mining_proxies: {},
chat_clients: [],
transactions: {},
wallet_addresses: {
"WALLET_B": "10039aa5ff194c75affcf08e62e19a88fcf483005f93d824bcb1a7e086060ba8b15106464fa34d0b9185d10e54584f8d7b2ba44589eff730211151692b7896ddf9038a",
},
utxos: {},
output_hash: None,
pre_image: None,
wallet_connected_to_base_node: {
"WALLET_A": "NODE",
"WALLET_B": "NODE",
"WALLET_C": "NODE",
},
seed_nodes: [
"NODE",
],
wallet_tx_ids: {
"H4AZKaqEZrLQAarJL4xmAday9SBbgRZG9N69Kd9eQV6xqArdeDeVNhfmHpsXFcoefJWyXdJBv9kLGBuWsEHpLZreApy": [
16663580844310336434,
],
"H4EeXnjDkKi3GrnHXHm9ZQGm3ng4LorcXueTvSHt2vFetjEq8Zsh9g3nt8DbGr7bq4fEKXP4Rtz9y7Bi63xjmShzziu": [
16663580844310336434,
],
},
errors: [],
last_imported_tx_ids: [
1951297141930487901,
],
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