Skip to content
CI

refactor: use workspace version #12973

Sign in to view logs

refactor: use workspace version

refactor: use workspace version #12973

Triggered via pull request April 15, 2024 13:16
@stringhandlerstringhandler
synchronize #6279
stringhandler:st-use-manifest-version
Status Success
Total duration 23m 38s
Artifacts 5

ci.yml

on: pull_request
clippy
7m 10s
clippy
machete
1m 15s
machete
cargo check with stable
8m 3s
cargo check with stable
file licenses
10s
file licenses
pr_2_artifact
8s
pr_2_artifact
Upload Event File for Test Results
4s
Upload Event File for Test Results
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

24 warnings and 3 notices
test (testnet, esmeralda)
Failed to restore: ENOENT: no such file or directory, scandir '/opt/hostedtoolcache/tari-project/tari'
test (mainnet, stagenet)
Failed to restore: ENOENT: no such file or directory, scandir '/opt/hostedtoolcache/tari-project/tari'
test (nextnet, nextnet)
Failed to restore: ENOENT: no such file or directory, scandir '/opt/hostedtoolcache/tari-project/tari'
1 out of 2 runs failed: Scenario: Verify UTXO and kernel MMR size in header: tests/features/BlockTemplate.feature:8:1: /#L0
artifacts/junit-cucumber/cucumber-output-junit.xml [took 10s]
1 out of 2 runs failed: Scenario: Verify gprc cna create block with more than 1 coinbase: tests/features/BlockTemplate.feature:14:5: /#L0
artifacts/junit-cucumber/cucumber-output-junit.xml [took 10s]
All 3 runs failed: Scenario: Transactions are propagated through a network: tests/features/Mempool.feature:8:3: /#L0
artifacts/junit-cucumber/cucumber-output-junit.xml [took 54s]
1 out of 2 runs failed: Scenario: Clear out mempool: tests/features/Mempool.feature:46:3: /#L0
artifacts/junit-cucumber/cucumber-output-junit.xml [took 10s]
1 out of 2 runs failed: Scenario: Zero-conf transactions: tests/features/Mempool.feature:124:3: /#L0
artifacts/junit-cucumber/cucumber-output-junit.xml [took 10s]
All 3 runs failed: Scenario: Simple reorg to stronger chain: tests/features/Reorgs.feature:8:3: /#L0
artifacts/junit-cucumber/cucumber-output-junit.xml [took 1m 0s]
All 3 runs failed: Scenario: Simple reorg with burned output: tests/features/Reorgs.feature:33:3: /#L0
artifacts/junit-cucumber/cucumber-output-junit.xml [took 10s]
1 out of 2 runs failed: Scenario: Simple block sync: tests/features/Sync.feature:26:3: /#L0
artifacts/junit-cucumber/cucumber-output-junit.xml [took 10s]
All 3 runs failed: Scenario: Sync burned output: tests/features/Sync.feature:34:3: /#L0
artifacts/junit-cucumber/cucumber-output-junit.xml [took 31s]
All 3 runs failed: Scenario: When a new node joins the network, it receives all peers: tests/features/Sync.feature:77:3: /#L0
artifacts/junit-cucumber/cucumber-output-junit.xml [took 26s]
All 3 runs failed: Scenario: Syncing node while also mining before tip sync: tests/features/Sync.feature:142:5: /#L0
artifacts/junit-cucumber/cucumber-output-junit.xml [took 10s]
All 3 runs failed: Scenario: As a wallet I want to submit a transaction: tests/features/WalletQuery.feature:18:3: /#L0
artifacts/junit-cucumber/cucumber-output-junit.xml [took 10s]
All 3 runs failed: Scenario: Wallet recovery with connected base node staying online: tests/features/WalletRecovery.feature:8:5: /#L0
artifacts/junit-cucumber/cucumber-output-junit.xml [took 10s]
All 3 runs failed: Scenario: Wallet sending and receiving one-sided transactions: tests/features/WalletTransactions.feature:8:3: /#L0
artifacts/junit-cucumber/cucumber-output-junit.xml [took 10s]
All 3 runs failed: Scenario: Create burn transaction: tests/features/WalletTransactions.feature:411:3: /#L0
artifacts/junit-cucumber/cucumber-output-junit.xml [took 10s]
All 3 runs failed: Scenario: As a wallet send to a wallet connected to a different base node: tests/features/WalletTransfer.feature:9:3: /#L0
artifacts/junit-cucumber/cucumber-output-junit.xml [took 10s]
1 out of 2 runs failed: Scenario: A message receives a delivery receipt via FFI: tests/features/ChatFFI.feature:78:3: /#L0
artifacts/junit-ffi-cucumber/cucumber-output-junit.xml [took 10s]
All 3 runs failed: Scenario: A message receives a read receipt via FFI: tests/features/ChatFFI.feature:86:3: /#L0
artifacts/junit-ffi-cucumber/cucumber-output-junit.xml [took 10s]
1 out of 2 runs failed: Scenario: Fetches all addresses from FFI conversations: tests/features/ChatFFI.feature:95:3: /#L0
artifacts/junit-ffi-cucumber/cucumber-output-junit.xml [took 10s]
All 3 runs failed: Scenario: A message is propagated between side loaded chat and client via 3rd party: tests/features/ChatFFI.feature:109:3: /#L0
artifacts/junit-ffi-cucumber/cucumber-output-junit.xml [took 10s]
All 3 runs failed: Scenario: As a client I want to receive contact liveness events: tests/features/WalletFFI.feature:73:5: /#L0
artifacts/junit-ffi-cucumber/cucumber-output-junit.xml [took 10s]
1278 tests found (test 1 to 799)
There are 1278 tests, see "Raw output" for the list of tests 1 to 799.
1278 tests found (test 800 to 1278)
There are 1278 tests, see "Raw output" for the list of tests 800 to 1278.
30 tests found
There are 30 tests, see "Raw output" for the full list of tests.

Artifacts

Produced during runtime
Name Size
Event File Expired
3.84 KB
pr_num Expired
141 Bytes
test-results-mainnet.stagenet Expired
26.6 KB
test-results-nextnet.nextnet Expired
25.2 KB
test-results-testnet.esmeralda Expired
26.9 KB