Skip to content
Source Coverage

feat: add dynamic growth to lmdb (#6231) #1457

Sign in to view logs

feat: add dynamic growth to lmdb (#6231)

feat: add dynamic growth to lmdb (#6231) #1457

Triggered via push March 26, 2024 12:41
@SWvheerdenSWvheerden
pushed f842c76
development
Status Failure
Total duration 9m 2s
Artifacts –

coverage.yml

on: push
test and generate coverage
8m 49s
test and generate coverage
Fit to window
Zoom out
Zoom in

Annotations

89 errors
test and generate coverage
Process completed with exit code 1.
test and generate coverage
Process completed with exit code 1.
minotari_wallet::wallet_integration_tests.transaction_service_tests::service::manage_multiple_transactions: minotari_wallet::wallet_integration_tests#L1
thread 'transaction_service_tests::service::manage_multiple_transactions' panicked at base_layer/wallet/tests/transaction_service_tests/service.rs:2198:5: assertion `left == right` failed
feature:7:3.Scenario: A message is propagated between clients via 3rd party: tests/features/ChatFFI.feature:7:3: feature:7:3#L1
Step panicked. Captured output: Service on port 18486 never started
feature:175:5.Scenario: As a client I want to send a one-sided transaction: tests/features/WalletFFI.feature:175:5: feature:175:5#L1
Step panicked. Captured output: Wallet RECEIVER failed to have at least num 1 txs with status 8, current status is 0
feature:175:5.Scenario: As a client I want to send a one-sided transaction: tests/features/WalletFFI.feature:175:5: feature:175:5#L1
Step panicked. Captured output: Wallet RECEIVER failed to have at least num 1 txs with status 8, current status is 0
feature:175:5.Scenario: As a client I want to send a one-sided transaction: tests/features/WalletFFI.feature:175:5: feature:175:5#L1
Step panicked. Captured output: Wallet RECEIVER failed to have at least num 1 txs with status 8, current status is 0
feature:212:5.Scenario: As a client I want to receive a one-sided transaction: tests/features/WalletFFI.feature:212:5: feature:212:5#L1
Step panicked. Captured output: Service on port 18277 never started
feature:212:5.Scenario: As a client I want to receive a one-sided transaction: tests/features/WalletFFI.feature:212:5: feature:212:5#L1
Step panicked. Captured output: Service on port 18130 never started
feature:212:5.Scenario: As a client I want to receive a one-sided transaction: tests/features/WalletFFI.feature:212:5: feature:212:5#L1
Step panicked. Captured output: Service on port 18204 never started
minotari_wallet::wallet_integration_tests.transaction_service_tests::service::manage_multiple_transactions: minotari_wallet::wallet_integration_tests#L1
thread 'transaction_service_tests::service::manage_multiple_transactions' panicked at base_layer/wallet/tests/transaction_service_tests/service.rs:2198:5: assertion `left == right` failed
tari_core.blocks::genesis_block::test::igor_genesis_sanity_check: tari_core#L1
thread 'blocks::genesis_block::test::igor_genesis_sanity_check' panicked at base_layer/core/src/blocks/genesis_block.rs:526:9: assertion `left == right` failed
tari_core.blocks::genesis_block::test::localnet_genesis_sanity_check: tari_core#L1
thread 'blocks::genesis_block::test::localnet_genesis_sanity_check' panicked at base_layer/core/src/blocks/genesis_block.rs:526:9: assertion `left == right` failed
tari_core.blocks::genesis_block::test::stagenet_genesis_sanity_check: tari_core#L1
thread 'blocks::genesis_block::test::stagenet_genesis_sanity_check' panicked at base_layer/core/src/blocks/genesis_block.rs:526:9: assertion `left == right` failed
feature:26:3.Scenario: Simple propagation: tests/features/Propagation.feature:26:3: feature:26:3#L1
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)
feature:7:3.Scenario: A message is propagated between clients via 3rd party: tests/features/ChatFFI.feature:7:3: feature:7:3#L1
Step panicked. Captured output: Service on port 18486 never started
feature:175:5.Scenario: As a client I want to send a one-sided transaction: tests/features/WalletFFI.feature:175:5: feature:175:5#L1
Step panicked. Captured output: Wallet RECEIVER failed to have at least num 1 txs with status 8, current status is 0
feature:175:5.Scenario: As a client I want to send a one-sided transaction: tests/features/WalletFFI.feature:175:5: feature:175:5#L1
Step panicked. Captured output: Wallet RECEIVER failed to have at least num 1 txs with status 8, current status is 0
feature:175:5.Scenario: As a client I want to send a one-sided transaction: tests/features/WalletFFI.feature:175:5: feature:175:5#L1
Step panicked. Captured output: Wallet RECEIVER failed to have at least num 1 txs with status 8, current status is 0
feature:212:5.Scenario: As a client I want to receive a one-sided transaction: tests/features/WalletFFI.feature:212:5: feature:212:5#L1
Step panicked. Captured output: Service on port 18277 never started
feature:212:5.Scenario: As a client I want to receive a one-sided transaction: tests/features/WalletFFI.feature:212:5: feature:212:5#L1
Step panicked. Captured output: Service on port 18130 never started
feature:212:5.Scenario: As a client I want to receive a one-sided transaction: tests/features/WalletFFI.feature:212:5: feature:212:5#L1
Step panicked. Captured output: Service on port 18204 never started
feature:8:1.Scenario: Verify UTXO and kernel MMR size in header: tests/features/BlockTemplate.feature:8:1: feature:8:1#L1
Step panicked. Captured output: Service on port 18359 never started
feature:8:1.Scenario: Verify UTXO and kernel MMR size in header: tests/features/BlockTemplate.feature:8:1: feature:8:1#L1
Step panicked. Captured output: Service on port 18211 never started
feature:8:1.Scenario: Verify UTXO and kernel MMR size in header: tests/features/BlockTemplate.feature:8:1: feature:8:1#L1
Step panicked. Captured output: Service on port 18057 never started
feature:8:3.Scenario: Transactions are propagated through a network: tests/features/Mempool.feature:8:3: feature:8:3#L1
Step panicked. Captured output: Service on port 18338 never started
feature:46:3.Scenario: Clear out mempool: tests/features/Mempool.feature:46:3: feature:46:3#L1
Step panicked. Captured output: Service on port 18359 never started
feature:124:3.Scenario: Zero-conf transactions: tests/features/Mempool.feature:124:3: feature:124:3#L1
Step panicked. Captured output: Service on port 18094 never started
feature:124:3.Scenario: Zero-conf transactions: tests/features/Mempool.feature:124:3: feature:124:3#L1
Step panicked. Captured output: Service on port 18103 never started
feature:46:3.Scenario: Clear out mempool: tests/features/Mempool.feature:46:3: feature:46:3#L1
Step panicked. Captured output: Service on port 18121 never started
feature:8:3.Scenario: Transactions are propagated through a network: tests/features/Mempool.feature:8:3: feature:8:3#L1
Step panicked. Captured output: Service on port 18465 never started
feature:8:3.Scenario: Transactions are propagated through a network: tests/features/Mempool.feature:8:3: feature:8:3#L1
Step panicked. Captured output: Service on port 18281 never started
feature:46:3.Scenario: Clear out mempool: tests/features/Mempool.feature:46:3: feature:46:3#L1
Step panicked. Captured output: Service on port 18010 never started
feature:124:3.Scenario: Zero-conf transactions: tests/features/Mempool.feature:124:3: feature:124:3#L1
Step panicked. Captured output: Service on port 18450 never started
feature:26:3.Scenario: Simple propagation: tests/features/Propagation.feature:26:3: feature:26:3#L1
Step panicked. Captured output: Service on port 18281 never started
feature:26:3.Scenario: Simple propagation: tests/features/Propagation.feature:26:3: feature:26:3#L1
Step panicked. Captured output: Service on port 18103 never started
feature:26:3.Scenario: Simple propagation: tests/features/Propagation.feature:26:3: feature:26:3#L1
Step panicked. Captured output: Service on port 18432 never started
feature:33:3.Scenario: Simple reorg with burned output: tests/features/Reorgs.feature:33:3: feature:33:3#L1
Step panicked. Captured output: Service on port 18152 never started
feature:142:5.Scenario: Syncing node while also mining before tip sync: tests/features/Sync.feature:142:5: feature:142:5#L1
Step panicked. Captured output: Service on port 18024 never started
feature:18:3.Scenario: As a wallet I want to submit a transaction: tests/features/WalletQuery.feature:18:3: feature:18:3#L1
Step panicked. Captured output: Service on port 18322 never started
feature:18:3.Scenario: As a wallet I want to submit a transaction: tests/features/WalletQuery.feature:18:3: feature:18:3#L1
Step panicked. Captured output: Service on port 18265 never started
feature:8:5.Scenario: Wallet recovery with connected base node staying online: tests/features/WalletRecovery.feature:8:5: feature:8:5#L1
Step panicked. Captured output: Service on port 18360 never started
feature:8:5.Scenario: Wallet recovery with connected base node staying online: tests/features/WalletRecovery.feature:8:5: feature:8:5#L1
Step panicked. Captured output: Service on port 18021 never started
feature:73:5.Scenario: As a client I want to receive contact liveness events: tests/features/WalletFFI.feature:73:5: feature:73:5#L1
Step panicked. Captured output: Service on port 18267 never started
feature:73:5.Scenario: As a client I want to receive contact liveness events: tests/features/WalletFFI.feature:73:5: feature:73:5#L1
Step panicked. Captured output: Service on port 18393 never started
feature:73:5.Scenario: As a client I want to receive contact liveness events: tests/features/WalletFFI.feature:73:5: feature:73:5#L1
Step panicked. Captured output: Service on port 18409 never started
feature:212:5.Scenario: As a client I want to receive a one-sided transaction: tests/features/WalletFFI.feature:212:5: feature:212:5#L1
Step panicked. Captured output: base nodes not successfully synchronized at height 12, {"SEED": 12, "BASE1": 12, "BASE2": 0}
tari_core.blocks::genesis_block::test::igor_genesis_sanity_check: tari_core#L1
thread 'blocks::genesis_block::test::igor_genesis_sanity_check' panicked at base_layer/core/src/blocks/genesis_block.rs:526:9: assertion `left == right` failed
tari_core.blocks::genesis_block::test::localnet_genesis_sanity_check: tari_core#L1
thread 'blocks::genesis_block::test::localnet_genesis_sanity_check' panicked at base_layer/core/src/blocks/genesis_block.rs:526:9: assertion `left == right` failed
feature:8:3.Scenario: Simple reorg to stronger chain: tests/features/Reorgs.feature:8:3: feature:8:3#L1
Step panicked. Captured output: Service on port 18433 never started
feature:33:3.Scenario: Simple reorg with burned output: tests/features/Reorgs.feature:33:3: feature:33:3#L1
Step panicked. Captured output: Service on port 18359 never started
feature:63:3.Scenario: Node rolls back reorg on invalid block: tests/features/Reorgs.feature:63:3: feature:63:3#L1
Step panicked. Captured output: Service on port 18362 never started
feature:63:3.Scenario: Node rolls back reorg on invalid block: tests/features/Reorgs.feature:63:3: feature:63:3#L1
Step panicked. Captured output: Service on port 18434 never started
feature:63:3.Scenario: Node rolls back reorg on invalid block: tests/features/Reorgs.feature:63:3: feature:63:3#L1
Step panicked. Captured output: Service on port 18197 never started
feature:8:3.Scenario: Simple reorg to stronger chain: tests/features/Reorgs.feature:8:3: feature:8:3#L1
Step panicked. Captured output: Service on port 18379 never started
feature:8:3.Scenario: Simple reorg to stronger chain: tests/features/Reorgs.feature:8:3: feature:8:3#L1
Step panicked. Captured output: Service on port 18460 never started
feature:33:3.Scenario: Simple reorg with burned output: tests/features/Reorgs.feature:33:3: feature:33:3#L1
Step panicked. Captured output: Service on port 18152 never started
feature:33:3.Scenario: Simple reorg with burned output: tests/features/Reorgs.feature:33:3: feature:33:3#L1
Step panicked. Captured output: Service on port 18344 never started
feature:26:3.Scenario: Simple block sync: tests/features/Sync.feature:26:3: feature:26:3#L1
Step panicked. Captured output: Service on port 18040 never started
feature:34:3.Scenario: Sync burned output: tests/features/Sync.feature:34:3: feature:34:3#L1
Step panicked. Captured output: Service on port 18135 never started
feature:26:3.Scenario: Simple block sync: tests/features/Sync.feature:26:3: feature:26:3#L1
Step panicked. Captured output: Service on port 18283 never started
feature:77:3.Scenario: When a new node joins the network, it receives all peers: tests/features/Sync.feature:77:3: feature:77:3#L1
Step panicked. Captured output: Service on port 18243 never started
feature:34:3.Scenario: Sync burned output: tests/features/Sync.feature:34:3: feature:34:3#L1
Step panicked. Captured output: Service on port 18111 never started
feature:26:3.Scenario: Simple block sync: tests/features/Sync.feature:26:3: feature:26:3#L1
Step panicked. Captured output: Service on port 18068 never started
feature:77:3.Scenario: When a new node joins the network, it receives all peers: tests/features/Sync.feature:77:3: feature:77:3#L1
Step panicked. Captured output: Service on port 18169 never started
feature:34:3.Scenario: Sync burned output: tests/features/Sync.feature:34:3: feature:34:3#L1
Step panicked. Captured output: Service on port 18415 never started
feature:142:5.Scenario: Syncing node while also mining before tip sync: tests/features/Sync.feature:142:5: feature:142:5#L1
Step panicked. Captured output: Service on port 18458 never started
feature:77:3.Scenario: When a new node joins the network, it receives all peers: tests/features/Sync.feature:77:3: feature:77:3#L1
Step panicked. Captured output: Service on port 18337 never started
feature:142:5.Scenario: Syncing node while also mining before tip sync: tests/features/Sync.feature:142:5: feature:142:5#L1
Step panicked. Captured output: Service on port 18108 never started
feature:142:5.Scenario: Syncing node while also mining before tip sync: tests/features/Sync.feature:142:5: feature:142:5#L1
Step panicked. Captured output: Service on port 18387 never started
feature:18:3.Scenario: As a wallet I want to submit a transaction: tests/features/WalletQuery.feature:18:3: feature:18:3#L1
Step panicked. Captured output: Service on port 18452 never started
feature:18:3.Scenario: As a wallet I want to submit a transaction: tests/features/WalletQuery.feature:18:3: feature:18:3#L1
Step panicked. Captured output: Service on port 18419 never started
feature:18:3.Scenario: As a wallet I want to submit a transaction: tests/features/WalletQuery.feature:18:3: feature:18:3#L1
Step panicked. Captured output: Service on port 18426 never started
feature:8:5.Scenario: Wallet recovery with connected base node staying online: tests/features/WalletRecovery.feature:8:5: feature:8:5#L1
Step panicked. Captured output: Service on port 18071 never started
feature:8:5.Scenario: Wallet recovery with connected base node staying online: tests/features/WalletRecovery.feature:8:5: feature:8:5#L1
Step panicked. Captured output: Service on port 18018 never started
feature:8:5.Scenario: Wallet recovery with connected base node staying online: tests/features/WalletRecovery.feature:8:5: feature:8:5#L1
Step panicked. Captured output: Service on port 18036 never started
feature:8:3.Scenario: Wallet sending and receiving one-sided transactions: tests/features/WalletTransactions.feature:8:3: feature:8:3#L1
Step panicked. Captured output: Service on port 18441 never started
feature:411:3.Scenario: Create burn transaction: tests/features/WalletTransactions.feature:411:3: feature:411:3#L1
Step panicked. Captured output: Service on port 18282 never started
feature:8:3.Scenario: Wallet sending and receiving one-sided transactions: tests/features/WalletTransactions.feature:8:3: feature:8:3#L1
Step panicked. Captured output: Service on port 18114 never started
feature:411:3.Scenario: Create burn transaction: tests/features/WalletTransactions.feature:411:3: feature:411:3#L1
Step panicked. Captured output: Service on port 18107 never started
feature:8:3.Scenario: Wallet sending and receiving one-sided transactions: tests/features/WalletTransactions.feature:8:3: feature:8:3#L1
Step panicked. Captured output: Service on port 18119 never started
feature:411:3.Scenario: Create burn transaction: tests/features/WalletTransactions.feature:411:3: feature:411:3#L1
Step panicked. Captured output: Service on port 18271 never started
feature:9:3.Scenario: As a wallet send to a wallet connected to a different base node: tests/features/WalletTransfer.feature:9:3: feature:9:3#L1
Step panicked. Captured output: Service on port 18274 never started
feature:9:3.Scenario: As a wallet send to a wallet connected to a different base node: tests/features/WalletTransfer.feature:9:3: feature:9:3#L1
Step panicked. Captured output: Service on port 18106 never started
feature:9:3.Scenario: As a wallet send to a wallet connected to a different base node: tests/features/WalletTransfer.feature:9:3: feature:9:3#L1
Step panicked. Captured output: Service on port 18230 never started
feature:175:5.Scenario: As a client I want to send a one-sided transaction: tests/features/WalletFFI.feature:175:5: feature:175:5#L1
Step panicked. Captured output: Wallet RECEIVER failed to have at least num 1 txs with status 8, current status is 0
minotari_mining_helper_ffi.tests::detect_change_in_consensus_encoding: minotari_mining_helper_ffi#L1
thread 'tests::detect_change_in_consensus_encoding' panicked at base_layer/tari_mining_helper_ffi/src/lib.rs:651:17: detect_change_in_consensus_encoding has failed. This might be a change in consensus encoding which requires an update to the pool miner code.
feature:212:5.Scenario: As a client I want to receive a one-sided transaction: tests/features/WalletFFI.feature:212:5: feature:212:5#L1
Step panicked. Captured output: base nodes not successfully synchronized at height 12, {"SEED": 12, "BASE1": 12, "BASE2": 0}
feature:212:5.Scenario: As a client I want to receive a one-sided transaction: tests/features/WalletFFI.feature:212:5: feature:212:5#L1
Step panicked. Captured output: base nodes not successfully synchronized at height 12, {"SEED": 12, "BASE1": 12, "BASE2": 0}