fix: avoid cloning range proofs during verification (#6166) #1411
SWvheerdencoverage.yml
on: push
test and generate coverage
5h 51m
Annotations
5 errors
|
feature:8:3.Scenario: Transactions are propagated through a network: tests/features/Mempool.feature:8:3:
feature:8: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:8:3.Scenario: Simple reorg to stronger chain: tests/features/Reorgs.feature:8:3:
feature:8: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: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 18059 never started
|
|
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: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
|