fix test
This check has been archived and is scheduled for deletion.
Learn more about checks retention
GitHub Actions / Test Results (Integration tests)
failed
Dec 1, 2023 in 0s
1 parse errors, 2 fail, 16 pass in 11m 39s
Annotations
Check failure on line 0 in artifacts/junit-ffi-cucumber/cucumber-output-junit.xml
github-actions / Test Results (Integration tests)
Error processing result file
File is empty.
Raw output
artifacts/junit-ffi-cucumber/cucumber-output-junit.xml
github-actions / Test Results (Integration tests)
All 3 runs failed: Scenario: Verify UTXO and kernel MMR size in header: tests/features/BlockTemplate.feature:8:1
artifacts/junit-cucumber/cucumber-output-junit.xml [took 0s]
Raw output
Step panicked. Captured output: assertion failed: `(left == right)` left: `"Chain storage error: Validation error: Block validation error: MMR size for Kernel does not match. Expected: 2, received: 3"`, right: `"Chain storage error: Validation error: Block validation error: MMR size for Kernel does not match. Expected: 3, received: 4"`
Scenario: Verify UTXO and kernel MMR size in header
✔ Given I have a seed node SEED_A
✔ When I have 1 base nodes connected to all seed nodes
✘ Then meddling with block template data from node SEED_A is not allowed
Step failed:
Defined: tests/features/BlockTemplate.feature:11:5
Matched: integration_tests/tests/steps/node_steps.rs:641:1
Step panicked. Captured output: assertion failed: `(left == right)`
left: `"Chain storage error: Validation error: Block validation error: MMR size for Kernel does not match. Expected: 2, received: 3"`,
right: `"Chain storage error: Validation error: Block validation error: MMR size for Kernel does not match. Expected: 3, received: 4"`
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: {},
seed_nodes: [
"SEED_A",
],
wallet_tx_ids: {},
errors: [],
last_imported_tx_ids: [],
last_merge_miner_response: Null,
}
github-actions / Test Results (Integration tests)
All 3 runs failed: Scenario: Simple Merge Mining: tests/features/MergeMining.feature:35:3
artifacts/junit-cucumber/cucumber-output-junit.xml [took 7s]
Raw output
Step panicked. Captured output: called `Result::unwrap()` on an `Err` value: reqwest::Error { kind: Request, url: Url { scheme: "http", cannot_be_a_base: false, username: "", password: None, host: Some(Ipv4(127.0.0.1)), port: Some(18470), path: "/json_rpc", query: None, fragment: None }, source: hyper::Error(Connect, ConnectError("tcp connect error", Os { code: 111, kind: ConnectionRefused, message: "Connection refused" })) }
Scenario: Simple Merge Mining
✔ Given I have a seed node NODE
✔ When I have wallet WALLET connected to all seed nodes
✔ And I have a merge mining proxy PROXY connected to NODE and WALLET with default config
✘ When I merge mine 2 blocks via PROXY
Step failed:
Defined: tests/features/MergeMining.feature:39:5
Matched: integration_tests/tests/steps/merge_mining_steps.rs:139:1
Step panicked. Captured output: called `Result::unwrap()` on an `Err` value: reqwest::Error { kind: Request, url: Url { scheme: "http", cannot_be_a_base: false, username: "", password: None, host: Some(Ipv4(127.0.0.1)), port: Some(18470), path: "/json_rpc", query: None, fragment: None }, source: hyper::Error(Connect, ConnectError("tcp connect error", Os { code: 111, kind: ConnectionRefused, message: "Connection refused" })) }
Client {
base_nodes: {},
blocks: {},
miners: {},
ffi_wallets: {},
wallets: {},
merge_mining_proxies: {
"PROXY": MergeMiningProxyProcess {
name: "PROXY",
base_node_name: "NODE",
wallet_name: "WALLET",
port: 18470,
origin_submission: true,
id: 1,
stealth: false,
},
},
chat_clients: [],
transactions: {},
wallet_addresses: {},
utxos: {},
output_hash: None,
pre_image: None,
wallet_connected_to_base_node: {
"WALLET": "NODE",
},
seed_nodes: [
"NODE",
],
wallet_tx_ids: {},
errors: [],
last_imported_tx_ids: [],
last_merge_miner_response: Null,
}
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: 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: Clear out mempool: tests/features/Mempool.feature:46:3
Scenario: Create burn transaction: tests/features/WalletTransactions.feature:411:3
Scenario: Node rolls back reorg on invalid block: tests/features/Reorgs.feature:63:3
Scenario: Simple Merge Mining: tests/features/MergeMining.feature:35: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