feat: fix tari pulse running as fast as possible (#6704) #1772
GitHub Actions / JUnit Test Report
failed
Nov 27, 2024 in 0s
27 tests run, 24 passed, 0 skipped, 3 failed.
Annotations
Check failure on line 1 in feature:8:3
github-actions / JUnit Test Report
feature:8:3.Scenario: Transactions are propagated through a network: tests/features/Mempool.feature:8:3
Step panicked. Captured output: Service 'Tcp' on port '18260' never started for 'Node_5'
Raw output
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 '18260' never started for 'Node_5'
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 failure on line 1 in feature:33:3
github-actions / JUnit Test Report
feature:33:3.Scenario: Simple reorg with burned output: tests/features/Reorgs.feature:33:3
Step panicked. Captured output: Service 'Tcp' on port '18431' never started for 'WC'
Raw output
Scenario: Simple reorg with burned output
Given I have a seed node SEED_B
When I have a base node B connected to seed SEED_B
When I have wallet WB connected to base node B
When I have mining node BM connected to base node B and wallet WB
When mining node BM mines 10 blocks with min difficulty 1 and max difficulty 1
When I wait for wallet WB to have at least 55000000000 uT
When I create a burn transaction of 1000000 uT from WB at fee 100
When mining node BM mines 5 blocks with min difficulty 1 and max difficulty 1
Given I have a seed node SEED_C
When I have a base node C connected to seed SEED_C
When I have wallet WC connected to base node C
Step failed:
Defined: tests/features/Reorgs.feature:50:5
Matched: integration_tests/tests/steps/wallet_steps.rs:159:1
Step panicked. Captured output: Service 'Tcp' on port '18431' never started for 'WC'
Client {
base_nodes: {},
blocks: {},
miners: {
"BM": MinerProcess {
name: "BM",
base_node_name: "B",
wallet_name: "WB",
mine_until_height: 100000,
stealth: false,
},
},
ffi_wallets: {},
wallets: {},
merge_mining_proxies: {},
transactions: {},
stopped_wallet_addresses: {},
utxos: {},
output_hash: None,
pre_image: None,
wallet_connected_to_base_node: {
"WB": "B",
"WC": "C",
},
seed_nodes: [
"SEED_B",
"SEED_C",
],
wallet_tx_ids: {},
errors: [],
last_imported_tx_ids: [],
last_merge_miner_response: Null,
}
Check failure on line 1 in feature:34:3
github-actions / JUnit Test Report
feature:34:3.Scenario: Sync burned output: tests/features/Sync.feature:34:3
Step panicked. Captured output: Service 'Tcp' on port '18294' never started for 'NODE'
Raw output
Scenario: Sync burned output
Given I have a seed node NODE
Step failed:
Defined: tests/features/Sync.feature:35:5
Matched: integration_tests/tests/steps/node_steps.rs:56:1
Step panicked. Captured output: Service 'Tcp' on port '18294' never started for 'NODE'
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: [
"NODE",
],
wallet_tx_ids: {},
errors: [],
last_imported_tx_ids: [],
last_merge_miner_response: Null,
}
Loading