Skip to content

feat!: update new block proto to support multiple coinbases (#6266) #1473

feat!: update new block proto to support multiple coinbases (#6266)

feat!: update new block proto to support multiple coinbases (#6266) #1473

Triggered via push April 15, 2024 11:06
Status Failure
Total duration 3m 38s
Artifacts

coverage.yml

on: push
test and generate coverage
2m 32s
test and generate coverage
Fit to window
Zoom out
Zoom in

Annotations

109 errors
test and generate coverage
Process completed with exit code 1.
test and generate coverage
Process completed with exit code 1.
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 18024 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 18402 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 18390 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 18116 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 18235 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 18311 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 18354 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 18358 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 18027 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 18384 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 18459 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 18391 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 18037 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 18190 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 18249 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 18297 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 18118 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 18198 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 18463 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 18246 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 18148 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 18080 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 18431 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 18458 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 18047 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 18061 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 18340 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 18317 never started
feature:78:3.Scenario: A message receives a delivery receipt via FFI: tests/features/ChatFFI.feature:78:3: feature:78:3#L1
Step panicked. Captured output: Service on port 18027 never started
feature:86:3.Scenario: A message receives a read receipt via FFI: tests/features/ChatFFI.feature:86:3: feature:86:3#L1
Step panicked. Captured output: Service on port 18046 never started
feature:86:3.Scenario: A message receives a read receipt via FFI: tests/features/ChatFFI.feature:86:3: feature:86:3#L1
Step panicked. Captured output: Service on port 18239 never started
feature:86:3.Scenario: A message receives a read receipt via FFI: tests/features/ChatFFI.feature:86:3: feature:86:3#L1
Step panicked. Captured output: Service on port 18030 never started
feature:95:3.Scenario: Fetches all addresses from FFI conversations: tests/features/ChatFFI.feature:95:3: feature:95:3#L1
Step panicked. Captured output: Service on port 18034 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
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: base nodes not successfully synchronized at height 12, {"SEED": 12, "BASE1": 12, "BASE2": 0}
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 18294 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 18272 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 18414 never started
feature:124:3.Scenario: Zero-conf transactions: tests/features/Mempool.feature:124:3: feature:124:3#L1
Step panicked. Captured output: called `Result::unwrap()` on an `Err` value: Status { code: Unavailable, message: "error trying to connect: tcp connect error: Connection refused (os error 111)", source: Some(tonic::transport::Error(Transport, hyper::Error(Connect, ConnectError("tcp connect error", Os { code: 111, kind: ConnectionRefused, message: "Connection refused" })))) }
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 18262 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 18258 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 18239 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 18220 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 18322 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 18234 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_comms_dht.connectivity::test::added_neighbours: tari_comms_dht#L1
thread 'connectivity::test::added_neighbours' panicked at comms/dht/src/connectivity/test.rs:151:5: assertion `left == right` failed
tari_comms_dht.connectivity::test::initialize: tari_comms_dht#L1
thread 'connectivity::test::initialize' panicked at comms/dht/src/connectivity/test.rs:114:5: Assertion failed. Expression was not true after 20 attempts.
tari_comms_dht.connectivity::test::replace_peer_when_peer_goes_offline: tari_comms_dht#L1
thread 'connectivity::test::replace_peer_when_peer_goes_offline' panicked at comms/dht/src/connectivity/test.rs:183:5: Assertion failed. Expression was not true after 20 attempts.
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 18138 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 18394 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 18175 never started
feature:96:5.Scenario: As a client I want to retrieve a list of transactions I have made and received: tests/features/WalletFFI.feature:96:5: feature:96:5#L1
Step panicked. Captured output: Wallet FFI_WALLET:18365 doesn't have enough available funds: available 0 incoming 2000000 time locked 0
feature:96:5.Scenario: As a client I want to retrieve a list of transactions I have made and received: tests/features/WalletFFI.feature:96:5: feature:96:5#L1
Step panicked. Captured output: Wallet FFI_WALLET:18189 doesn't have enough available funds: available 0 incoming 2000000 time locked 0
feature:96:5.Scenario: As a client I want to retrieve a list of transactions I have made and received: tests/features/WalletFFI.feature:96:5: feature:96:5#L1
Step panicked. Captured output: Wallet FFI_WALLET:18369 doesn't have enough available funds: available 0 incoming 2000000 time locked 0
tari_comms_dht::attacks.large_join_messages_with_many_addresses: tari_comms_dht::attacks#L1
thread 'large_join_messages_with_many_addresses' panicked at comms/dht/tests/attacks.rs:63:10: called `Result::unwrap()` on an `Err` value: OnlineWaitTimeout(0)
tari_comms_dht::dht.test_dht_join_propagation: tari_comms_dht::dht#L1
thread 'test_dht_join_propagation' panicked at comms/dht/tests/dht.rs:934:14: called `Result::unwrap()` on an `Err` value: OnlineWaitTimeout(0)
tari_comms_dht::dht.test_dht_header_not_malleable: tari_comms_dht::dht#L1
thread 'test_dht_header_not_malleable' panicked at /runner/_work/tari/tari/infrastructure/test_utils/src/streams/mod.rs:253:14: Timeout before stream emitted: Elapsed(())
tari_comms_dht::dht.test_dht_propagate_message_contents_not_malleable_ban: tari_comms_dht::dht#L1
thread 'test_dht_propagate_message_contents_not_malleable_ban' panicked at /runner/_work/tari/tari/infrastructure/test_utils/src/streams/mod.rs:253:14: Timeout before stream emitted: Elapsed(())
tari_comms_dht::dht.test_dht_discover_propagation: tari_comms_dht::dht#L1
thread 'test_dht_discover_propagation' panicked at comms/dht/tests/dht.rs:934:14: called `Result::unwrap()` on an `Err` value: OnlineWaitTimeout(0)
tari_comms_dht::dht.test_dht_store_forward: tari_comms_dht::dht#L1
thread 'test_dht_store_forward' panicked at comms/dht/tests/dht.rs:934:14: called `Result::unwrap()` on an `Err` value: OnlineWaitTimeout(0)
tari_p2p::mod.services::liveness::end_to_end: tari_p2p::mod#L1
thread 'services::liveness::end_to_end' panicked at /runner/_work/tari/tari/base_layer/service_framework/src/context/handles.rs:189:21: Service handle `alloc::sync::Arc<tari_comms::peer_manager::manager::PeerManager>` is not registered
tari_core::core_integration_tests.tests::block_sync::test_block_sync_peer_supplies_not_all_blocks_with_ban: tari_core::core_integration_tests#L1
thread 'tokio-runtime-worker' panicked at /runner/_work/tari/tari/base_layer/service_framework/src/context/handles.rs:189:21: Service handle `alloc::sync::Arc<tari_comms::peer_manager::manager::PeerManager>` is not registered
tari_core::core_integration_tests.tests::block_sync::test_block_sync_with_conbase_spend_happy_path_1: tari_core::core_integration_tests#L1
thread 'tokio-runtime-worker' panicked at /runner/_work/tari/tari/base_layer/service_framework/src/context/handles.rs:189:21: Service handle `alloc::sync::Arc<tari_comms::peer_manager::manager::PeerManager>` is not registered
tari_core::core_integration_tests.tests::block_sync::test_block_sync_happy_path: tari_core::core_integration_tests#L1
thread 'tokio-runtime-worker' panicked at /runner/_work/tari/tari/base_layer/service_framework/src/context/handles.rs:189:21: Service handle `alloc::sync::Arc<tari_comms::peer_manager::manager::PeerManager>` is not registered
tari_core::core_integration_tests.tests::block_sync::test_block_sync_peer_supplies_no_blocks_with_ban: tari_core::core_integration_tests#L1
thread 'tokio-runtime-worker' panicked at /runner/_work/tari/tari/base_layer/service_framework/src/context/handles.rs:189:21: Service handle `alloc::sync::Arc<tari_comms::peer_manager::manager::PeerManager>` is not registered
tari_core::core_integration_tests.tests::block_sync::test_block_sync_with_conbase_spend_happy_path_2: tari_core::core_integration_tests#L1
thread 'tokio-runtime-worker' panicked at /runner/_work/tari/tari/base_layer/service_framework/src/context/handles.rs:189:21: Service handle `alloc::sync::Arc<tari_comms::peer_manager::manager::PeerManager>` is not registered
tari_core::core_integration_tests.tests::header_sync::test_header_sync_even_headers_and_blocks_peer_lies_about_pow_with_ban: tari_core::core_integration_tests#L1
thread 'tokio-runtime-worker' panicked at /runner/_work/tari/tari/base_layer/service_framework/src/context/handles.rs:189:21: Service handle `alloc::sync::Arc<tari_comms::peer_manager::manager::PeerManager>` is not registered
tari_core::core_integration_tests.tests::header_sync::test_header_sync_even_headers_and_blocks_peer_metadata_improve_with_reorg: tari_core::core_integration_tests#L1
thread 'tokio-runtime-worker' panicked at /runner/_work/tari/tari/base_layer/service_framework/src/context/handles.rs:189:21: Service handle `alloc::sync::Arc<tari_comms::peer_manager::manager::PeerManager>` is not registered
tari_core::core_integration_tests.tests::header_sync::test_header_sync_happy_path: tari_core::core_integration_tests#L1
thread 'tokio-runtime-worker' panicked at /runner/_work/tari/tari/base_layer/service_framework/src/context/handles.rs:189:21: Service handle `alloc::sync::Arc<tari_comms::peer_manager::manager::PeerManager>` is not registered
tari_core::core_integration_tests.tests::header_sync::test_header_sync_uneven_headers_and_blocks_happy_path: tari_core::core_integration_tests#L1
thread 'tokio-runtime-worker' panicked at /runner/_work/tari/tari/base_layer/service_framework/src/context/handles.rs:189:21: Service handle `alloc::sync::Arc<tari_comms::peer_manager::manager::PeerManager>` is not registered
tari_core::core_integration_tests.tests::header_sync::test_header_sync_uneven_headers_and_blocks_peer_lies_about_pow_no_ban: tari_core::core_integration_tests#L1
thread 'tokio-runtime-worker' panicked at /runner/_work/tari/tari/base_layer/service_framework/src/context/handles.rs:189:21: Service handle `alloc::sync::Arc<tari_comms::peer_manager::manager::PeerManager>` is not registered
tari_core::core_integration_tests.tests::horizon_sync::test_consecutive_horizon_sync_from_prune_node_happy_path: tari_core::core_integration_tests#L1
thread 'tokio-runtime-worker' panicked at /runner/_work/tari/tari/base_layer/service_framework/src/context/handles.rs:189:21: Service handle `alloc::sync::Arc<tari_comms::peer_manager::manager::PeerManager>` is not registered
tari_core::core_integration_tests.tests::horizon_sync::test_initial_horizon_sync_from_archival_node_happy_path: tari_core::core_integration_tests#L1
thread 'tokio-runtime-worker' panicked at /runner/_work/tari/tari/base_layer/service_framework/src/context/handles.rs:189:21: Service handle `alloc::sync::Arc<tari_comms::peer_manager::manager::PeerManager>` is not registered
tari_core::core_integration_tests.tests::horizon_sync::test_initial_horizon_sync_from_prune_node_happy_path: tari_core::core_integration_tests#L1
thread 'tokio-runtime-worker' panicked at /runner/_work/tari/tari/base_layer/service_framework/src/context/handles.rs:189:21: Service handle `alloc::sync::Arc<tari_comms::peer_manager::manager::PeerManager>` is not registered
tari_core::core_integration_tests.tests::mempool::block_event_and_reorg_event_handling: tari_core::core_integration_tests#L1
thread 'tests::mempool::block_event_and_reorg_event_handling' panicked at /runner/_work/tari/tari/base_layer/service_framework/src/context/handles.rs:189:21: Service handle `alloc::sync::Arc<tari_comms::peer_manager::manager::PeerManager>` is not registered
tari_core::core_integration_tests.tests::mempool::receive_and_propagate_transaction: tari_core::core_integration_tests#L1
thread 'tokio-runtime-worker' panicked at /runner/_work/tari/tari/base_layer/service_framework/src/context/handles.rs:189:21: Service handle `alloc::sync::Arc<tari_comms::peer_manager::manager::PeerManager>` is not registered
tari_core::core_integration_tests.tests::node_service::propagate_and_forward_invalid_block: tari_core::core_integration_tests#L1
thread 'tokio-runtime-worker' panicked at /runner/_work/tari/tari/base_layer/service_framework/src/context/handles.rs:189:21: Service handle `alloc::sync::Arc<tari_comms::peer_manager::manager::PeerManager>` is not registered
tari_core::core_integration_tests.tests::node_service::propagate_and_forward_invalid_block_hash: tari_core::core_integration_tests#L1
thread 'tokio-runtime-worker' panicked at /runner/_work/tari/tari/base_layer/service_framework/src/context/handles.rs:189:21: Service handle `alloc::sync::Arc<tari_comms::peer_manager::manager::PeerManager>` is not registered
tari_core::core_integration_tests.tests::node_service::propagate_and_forward_many_valid_blocks: tari_core::core_integration_tests#L1
thread 'tokio-runtime-worker' panicked at /runner/_work/tari/tari/base_layer/service_framework/src/context/handles.rs:189:21: Service handle `alloc::sync::Arc<tari_comms::peer_manager::manager::PeerManager>` is not registered
tari_core::core_integration_tests.tests::node_state_machine::test_listening_initial_fallen_behind: tari_core::core_integration_tests#L1
thread 'tokio-runtime-worker' panicked at /runner/_work/tari/tari/base_layer/service_framework/src/context/handles.rs:189:21: Service handle `alloc::sync::Arc<tari_comms::peer_manager::manager::PeerManager>` is not registered
tari_core::core_integration_tests.tests::node_state_machine::test_listening_lagging: tari_core::core_integration_tests#L1
thread 'tokio-runtime-worker' panicked at /runner/_work/tari/tari/base_layer/service_framework/src/context/handles.rs:189:21: Service handle `alloc::sync::Arc<tari_comms::peer_manager::manager::PeerManager>` is not registered
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 18423 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 18486 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 18054 never started
feature:96:5.Scenario: As a client I want to retrieve a list of transactions I have made and received: tests/features/WalletFFI.feature:96:5: feature:96:5#L1
Step panicked. Captured output: Wallet FFI_WALLET:18297 doesn't have enough available funds: available 0 incoming 2000000 time locked 0
feature:96:5.Scenario: As a client I want to retrieve a list of transactions I have made and received: tests/features/WalletFFI.feature:96:5: feature:96:5#L1
Step panicked. Captured output: Wallet FFI_WALLET:18090 doesn't have enough available funds: available 0 incoming 2000000 time locked 0
feature:96:5.Scenario: As a client I want to retrieve a list of transactions I have made and received: tests/features/WalletFFI.feature:96:5: feature:96:5#L1
Step panicked. Captured output: Wallet FFI_WALLET:18004 doesn't have enough available funds: available 0 incoming 2000000 time locked 0