feat: generate script challenge on the ledger (#6344) #1512
SWvheerdencoverage.yml
on: push
test and generate coverage
2m 48s
Annotations
18 errors
|
test and generate coverage
Process completed with exit code 1.
|
|
test and generate coverage
Process completed with exit code 1.
|
|
tari_core.blocks::genesis_block::test::esme_genesis_sanity_check:
tari_core#L1
thread 'blocks::genesis_block::test::esme_genesis_sanity_check' panicked at base_layer/core/src/blocks/genesis_block.rs:469:69:
called `Result::unwrap()` on an `Err` value: InvalidRangeProof { reason: "Signature is invalid: Metadata signature not valid!" }
|
|
feature:8:3.Scenario: Transactions are propagated through a network: tests/features/Mempool.feature:8:3:
feature:8:3#L1
Step panicked. Captured output: status: InvalidArgument, message: "Invalid transaction provided: outputs Incorrect length: Expected 80, 84, 88 or 112 bytes, got 0", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc", "date": "Mon, 20 May 2024 07:33:12 GMT", "content-length": "0"} }
|
|
feature:46:3.Scenario: Clear out mempool: tests/features/Mempool.feature:46:3:
feature:46:3#L1
Step panicked. Captured output: status: InvalidArgument, message: "Invalid transaction provided: outputs Incorrect length: Expected 80, 84, 88 or 112 bytes, got 0", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc", "date": "Mon, 20 May 2024 07:32:58 GMT", "content-length": "0"} }
|
|
feature:124:3.Scenario: Zero-conf transactions: tests/features/Mempool.feature:124:3:
feature:124:3#L1
Step panicked. Captured output: status: InvalidArgument, message: "Invalid transaction provided: outputs Incorrect length: Expected 80, 84, 88 or 112 bytes, got 0", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc", "date": "Mon, 20 May 2024 07:32:58 GMT", "content-length": "0"} }
|
|
feature:124:3.Scenario: Zero-conf transactions: tests/features/Mempool.feature:124:3:
feature:124:3#L1
Step panicked. Captured output: status: InvalidArgument, message: "Invalid transaction provided: outputs Incorrect length: Expected 80, 84, 88 or 112 bytes, got 0", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc", "date": "Mon, 20 May 2024 07:33:05 GMT", "content-length": "0"} }
|
|
feature:46:3.Scenario: Clear out mempool: tests/features/Mempool.feature:46:3:
feature:46:3#L1
Step panicked. Captured output: status: InvalidArgument, message: "Invalid transaction provided: outputs Incorrect length: Expected 80, 84, 88 or 112 bytes, got 0", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc", "date": "Mon, 20 May 2024 07:33:05 GMT", "content-length": "0"} }
|
|
feature:46:3.Scenario: Clear out mempool: tests/features/Mempool.feature:46:3:
feature:46:3#L1
Step panicked. Captured output: status: InvalidArgument, message: "Invalid transaction provided: outputs Incorrect length: Expected 80, 84, 88 or 112 bytes, got 0", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc", "date": "Mon, 20 May 2024 07:33:11 GMT", "content-length": "0"} }
|
|
feature:124:3.Scenario: Zero-conf transactions: tests/features/Mempool.feature:124:3:
feature:124:3#L1
Step panicked. Captured output: status: InvalidArgument, message: "Invalid transaction provided: outputs Incorrect length: Expected 80, 84, 88 or 112 bytes, got 0", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc", "date": "Mon, 20 May 2024 07:33:12 GMT", "content-length": "0"} }
|
|
feature:8:3.Scenario: Transactions are propagated through a network: tests/features/Mempool.feature:8:3:
feature:8:3#L1
Step panicked. Captured output: status: InvalidArgument, message: "Invalid transaction provided: outputs Incorrect length: Expected 80, 84, 88 or 112 bytes, got 0", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc", "date": "Mon, 20 May 2024 07:33:33 GMT", "content-length": "0"} }
|
|
feature:8:3.Scenario: Transactions are propagated through a network: tests/features/Mempool.feature:8:3:
feature:8:3#L1
Step panicked. Captured output: status: InvalidArgument, message: "Invalid transaction provided: outputs Incorrect length: Expected 80, 84, 88 or 112 bytes, got 0", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc", "date": "Mon, 20 May 2024 07:33:52 GMT", "content-length": "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 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 18140 never started
|
|
tari_p2p::mod.services::liveness::end_to_end:
tari_p2p::mod#L1
thread 'services::liveness::end_to_end' panicked at base_layer/p2p/tests/services/liveness.rs:120:18:
Timeout before stream could collect 18 item(s). Got 8 item(s).: Elapsed(())
|
|
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
|