Skip to content
Source Coverage

chore: new release for esme (#6157) #1407

Sign in to view logs

chore: new release for esme (#6157)

chore: new release for esme (#6157) #1407

Triggered via push February 20, 2024 11:04
@SWvheerdenSWvheerden
pushed f5860a8
development
Status Failure
Total duration 6h 0m 46s
Artifacts –

coverage.yml

on: push
test and generate coverage
6h 0m
test and generate coverage
Fit to window
Zoom out
Zoom in

Annotations

26 errors
minotari_wallet::wallet_integration_tests.transaction_service_tests::service::test_spend_dust_to_self_in_oversized_transaction: minotari_wallet::wallet_integration_tests#L1
transaction_service_tests::service::test_spend_dust_to_self_in_oversized_transaction
tari_core::core_integration_tests.tests::node_state_machine::test_listening_initial_fallen_behind: tari_core::core_integration_tests#L1
thread 'tests::node_state_machine::test_listening_initial_fallen_behind' panicked at 'assertion failed: `(left == right)` left: `1`,
feature:33:3.Scenario: Simple reorg with burned output: tests/features/Reorgs.feature:33:3: feature:33:3#L1
Step panicked. Captured output: Burn transaction has status 0 when we desired 1 (TRANSACTION_STATUS_BROADCAST), 2 (TRANSACTION_STATUS_UNCONFIRMED), or 6 (TRANSACTION_STATUS_CONFIRMED)
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 18051 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 18074 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 18193 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 18298 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 18247 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 18106 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 18432 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 18245 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 18093 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 18325 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 18144 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 18333 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 18050 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 18054 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 18203 never started
feature:26:3.Scenario: Simple propagation: tests/features/Propagation.feature:26:3: feature:26:3#L1
Step panicked. Captured output: base nodes not successfully synchronized at height 5, {"seed_node_0": 9, "seed_node_1": 9, "Node_0": 9, "Node_1": 9, "Node_2": 9, "Node_3": 9, "MINER": 5}
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: One sided transaction from WALLET_A to WALLET_B with amount 1000000 at fee 100 failed to be broadcasted
test and generate coverage
The job running on runner hetzner-generic-runner-jcf5z-786jc has exceeded the maximum execution time of 360 minutes.
test and generate coverage
The operation was canceled.
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 'assertion failed: `(left == right)` left: `1`,
feature:34:3.Scenario: Sync burned output: tests/features/Sync.feature:34:3: feature:34:3#L1
Step panicked. Captured output: Burn transaction has status 0 when we desired 1 (TRANSACTION_STATUS_BROADCAST), 2 (TRANSACTION_STATUS_UNCONFIRMED), or 6 (TRANSACTION_STATUS_CONFIRMED)
feature:33:3.Scenario: Simple reorg with burned output: tests/features/Reorgs.feature:33:3: feature:33:3#L1
Step panicked. Captured output: base node didn't synchronize successfully with height 17, current chain height 0
feature:33:3.Scenario: Simple reorg with burned output: tests/features/Reorgs.feature:33:3: feature:33:3#L1
Step panicked. Captured output: Burn transaction has status 0 when we desired 1 (TRANSACTION_STATUS_BROADCAST), 2 (TRANSACTION_STATUS_UNCONFIRMED), or 6 (TRANSACTION_STATUS_CONFIRMED)