Skip to content

ci(fix): add weekly dual arch docker builds with tags plus network (#… #1156

ci(fix): add weekly dual arch docker builds with tags plus network (#…

ci(fix): add weekly dual arch docker builds with tags plus network (#… #1156

Triggered via push September 6, 2023 08:51
Status Success
Total duration 3h 50m 9s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

coverage.yml

on: push
test and generate coverage
3h 49m
test and generate coverage
Fit to window
Zoom out
Zoom in

Annotations

32 errors
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 'called `Result::unwrap()` on an `Err` value: OutputManagerError(OutputManagerStorageError(DieselError(DatabaseError(Unknown, "database is locked"))))', base_layer/wallet/tests/transaction_service_tests/service.rs:1536:10 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
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 18072 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 18323 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 18237 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 18306 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 18209 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 18097 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 18393 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 18096 never started
feature:50:3.Scenario: Pruned mode simple sync: tests/features/Sync.feature:50:3: feature:50:3#L1
Step panicked. Captured output: Service on port 18458 never started
feature:50:3.Scenario: Pruned mode simple sync: tests/features/Sync.feature:50:3: feature:50:3#L1
Step panicked. Captured output: Service on port 18017 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 18032 never started
feature:50:3.Scenario: Pruned mode simple sync: tests/features/Sync.feature:50:3: feature:50:3#L1
Step panicked. Captured output: Service on port 18198 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 18426 never started
feature:61:3.Scenario: Pruned node should handle burned output: tests/features/Sync.feature:61:3: feature:61:3#L1
Step panicked. Captured output: Service on port 18446 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 18197 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 18426 never started
feature:61:3.Scenario: Pruned node should handle burned output: tests/features/Sync.feature:61:3: feature:61:3#L1
Step panicked. Captured output: Service on port 18244 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 18360 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 18081 never started
feature:61:3.Scenario: Pruned node should handle burned output: tests/features/Sync.feature:61:3: feature:61:3#L1
Step panicked. Captured output: Service on port 18080 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 18425 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 18031 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 18185 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 18449 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 18010 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 18505 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 18250 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 9, current status is 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 RECEIVER failed to have at least num 1 txs with status 1, current status is 0