PR

refactor: better network global #10817

Sign in to view logs

Triggered via pull request December 5, 2023 13:25

synchronize #6014

stringhandler:st-better-network-design

Status Success

Total duration 18s

Artifacts –

This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

pr_title.yml

on: pull_request

Annotations

30 warnings and 3 notices

All 3 runs failed: Scenario: Callback for new message received: tests/features/ChatFFI.feature:14:3: /#L0

artifacts/junit-ffi-cucumber/cucumber-output-junit.xml [took 10s]

All 3 runs failed: Scenario: Callback for delivery confirmation received: tests/features/ChatFFI.feature:22:3: /#L0

artifacts/junit-ffi-cucumber/cucumber-output-junit.xml [took 10s]

All 3 runs failed: Scenario: Callback for read confirmation received: tests/features/ChatFFI.feature:31:3: /#L0

artifacts/junit-ffi-cucumber/cucumber-output-junit.xml [took 10s]

All 3 runs failed: Scenario: Chat shuts down without any errors: tests/features/ChatFFI.feature:63:3: /#L0

artifacts/junit-ffi-cucumber/cucumber-output-junit.xml [took 10s]

All 3 runs failed: Scenario: Reply to message: tests/features/ChatFFI.feature:68:3: /#L0

artifacts/junit-ffi-cucumber/cucumber-output-junit.xml [took 10s]

All 3 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]

All 3 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: 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]

All 3 runs failed: Scenario: As a client I want to retrieve a list of transactions I have made and received: tests/features/WalletFFI.feature:96:5: /#L0

artifacts/junit-ffi-cucumber/cucumber-output-junit.xml [took 10s]

All 3 runs failed: Scenario: As a client I want to send a one-sided transaction: tests/features/WalletFFI.feature:175:5: /#L0

artifacts/junit-ffi-cucumber/cucumber-output-junit.xml [took 10s]

All 3 runs failed: Scenario: As a client I want to receive a one-sided transaction: tests/features/WalletFFI.feature:212:5: /#L0

artifacts/junit-ffi-cucumber/cucumber-output-junit.xml [took 10s]

All 3 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]

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 10s]

All 3 runs failed: Scenario: Clear out mempool: tests/features/Mempool.feature:46:3: /#L0

artifacts/junit-cucumber/cucumber-output-junit.xml [took 10s]

All 3 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 Merge Mining: tests/features/MergeMining.feature:35:3: /#L0

artifacts/junit-cucumber/cucumber-output-junit.xml [took 10s]

All 3 runs failed: Scenario: Simple propagation: tests/features/Propagation.feature:26: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 10s]

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]

All 3 runs failed: Scenario: Node rolls back reorg on invalid block: tests/features/Reorgs.feature:63:3: /#L0

artifacts/junit-cucumber/cucumber-output-junit.xml [took 10s]

All 3 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 10s]

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 10s]

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]

1261 tests found (test 1 to 799)

There are 1261 tests, see "Raw output" for the list of tests 1 to 799.

1261 tests found (test 800 to 1261)

There are 1261 tests, see "Raw output" for the list of tests 800 to 1261.

32 tests found

There are 32 tests, see "Raw output" for the full list of tests.