Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: adjust block sync timeouts #6342

Merged

Adjust block sync timeouts

25d4b93
Select commit
Loading
Failed to load commit list.
Sign in for the full log view
Merged

feat: adjust block sync timeouts #6342

Adjust block sync timeouts
25d4b93
Select commit
Loading
Failed to load commit list.
GitHub Actions / Test Results (Integration tests) failed May 16, 2024 in 0s

3 fail, 30 pass in 25m 3s

 2 files  11 suites   25m 3s ⏱️
33 tests 30 ✅ 0 💤 3 ❌
37 runs  32 ✅ 0 💤 5 ❌

Results for commit 25d4b93.

Annotations

Check warning on line 0 in /

See this annotation in the file changed.

@github-actions github-actions / Test Results (Integration tests)

1 out of 2 runs failed: Scenario: As a client I want to send a one-sided transaction: tests/features/WalletFFI.feature:175:5

artifacts/junit-ffi-cucumber/cucumber-output-junit.xml [took 9m 3s]
Raw output
Step panicked. Captured output: Wallet RECEIVER failed to have at least num 1 txs with status 8, current status is 0
  Scenario: As a client I want to send a one-sided transaction
   ✔  Given I have a seed node SEED
   ✔  When I have a base node BASE1 connected to all seed nodes
   ✔  When I have wallet SENDER connected to base node BASE1
   ✔  And I have a ffi wallet FFI_WALLET connected to base node SEED
   ✔  When I have wallet RECEIVER connected to base node BASE1
   ✔  When I add contact with alias ALIAS1 and address of SENDER to ffi wallet FFI_WALLET
   ✔  When I add contact with alias ALIAS2 and address of RECEIVER to ffi wallet FFI_WALLET
   ✔  When I have mining node MINER connected to base node BASE1 and wallet SENDER
   ✔  When mining node MINER mines 10 blocks
   ✔  Then all nodes are at height 10
   ✔  Then I wait for wallet SENDER to have at least 129239250000 uT
   ✔  And I send 2400000 uT from wallet SENDER to wallet FFI_WALLET at fee 5
   ✔  And I send 2400000 uT from wallet SENDER to wallet FFI_WALLET at fee 5
   ✔  Then wallet SENDER has at least 2 transactions that are all TRANSACTION_STATUS_BROADCAST and not cancelled
   ✔  Then ffi wallet FFI_WALLET detects AT_LEAST 2 ffi transactions to be TRANSACTION_STATUS_BROADCAST
   ✔  When mining node MINER mines 10 blocks
   ✔  Then all nodes are at height 20
   ✔  Then ffi wallet FFI_WALLET detects AT_LEAST 2 ffi transactions to be TRANSACTION_STATUS_MINED
   ✔  Then I wait for ffi wallet FFI_WALLET to have at least 4000000 uT
   ✔  And I send 1000000 uT from ffi wallet FFI_WALLET to wallet RECEIVER at fee 5 via one-sided transactions
   ✔  Then ffi wallet FFI_WALLET detects AT_LEAST 3 ffi transactions to be TRANSACTION_STATUS_BROADCAST
   ✔  When mining node MINER mines 2 blocks
   ✔  Then all nodes are at height 22
   ✘  Then wallet RECEIVER has at least 1 transactions that are all TRANSACTION_STATUS_ONE_SIDED_UNCONFIRMED and not cancelled
      Step failed:
      Defined: tests/features/WalletFFI.feature:205:9
      Matched: integration_tests/tests/steps/wallet_steps.rs:514:1
      Step panicked. Captured output: Wallet RECEIVER failed to have at least num 1 txs with status 8, current status is 0
      Client {
          base_nodes: {},
          blocks: {},
          miners: {
              "MINER": MinerProcess {
                  name: "MINER",
                  base_node_name: "BASE1",
                  wallet_name: "SENDER",
                  mine_until_height: 100000,
                  stealth: false,
              },
          },
          ffi_wallets: {
              "FFI_WALLET": WalletFFI {
                  name: "FFI_WALLET",
                  port: 18093,
                  base_dir: "/runner/_work/tari/tari/integration_tests/tests/temp/cucumber_6432/Wallet FFI/As a client I want to send a one-sided transaction/ffi_wallets/FFI_WALLET_port_18093",
                  wallet: Mutex {
                      data: Wallet {
                          ptr: 0x00007f6d28037110,
                          liveness_data: Mutex {
                              data: {
                                  "ccb8429df8bbec10102e852d614ff9f738314929184c501e321bee33a329213fd9": ContactsLivenessData {
                                      ptr: 0x00007f6b840e86a0,
                                  },
                                  "260b2a3893424cb4827c6e7a80a262a14e163bc642fe4d81298ca4252a3a2039ef": ContactsLivenessData {
                                      ptr: 0x00007f69e40747e0,
                                  },
                              },
                              poisoned: false,
                              ..
                          },
                          balance: CachedBalance {
                              available: 2400000,
                              time_locked: 0,
                              pending_incoming: 1399330,
                              pending_outgoing: 2400000,
                          },
                      },
                      poisoned: false,
                      ..
                  },
              },
          },
          wallets: {},
          merge_mining_proxies: {},
          chat_clients: [],
          transactions: {},
          wallet_addresses: {},
          utxos: {},
          output_hash: None,
          pre_image: None,
          wallet_connected_to_base_node: {
              "SENDER": "BASE1",
              "RECEIVER": "BASE1",
          },
          seed_nodes: [
              "SEED",
          ],
          wallet_tx_ids: {
              "ccb8429df8bbec10102e852d614ff9f738314929184c501e321bee33a329213fd9": [
                  10594587666557928970,
                  14731422326718519952,
              ],
              "2a10dfc8ba719911e222914cb7184c50d32eb44354614538d400787477a0076eaf": [
                  10594587666557928970,
                  14731422326718519952,
              ],
          },
          errors: [],
          last_imported_tx_ids: [],
          last_merge_miner_response: Null,
      }

Check warning on line 0 in /

See this annotation in the file changed.

@github-actions github-actions / Test Results (Integration tests)

1 out of 2 runs failed: Scenario: When a new node joins the network, it receives all peers: tests/features/Sync.feature:77:3

artifacts/junit-cucumber/cucumber-output-junit.xml [took 2m 6s]
Raw output
Step panicked. Captured output: Node NODE2 only received 10 of 11 expected peers
  Scenario: When a new node joins the network, it receives all peers
   ✔  Given I have 10 seed nodes
   ✔  When I have a base node NODE1 connected to all seed nodes
   ✔  When I wait for NODE1 to have 10 connections
   ✔  When I have a base node NODE2 connected to node NODE1
   ✔  Then NODE1 has at least 11 peers
   ✘  Then NODE2 has at least 11 peers
      Step failed:
      Defined: tests/features/Sync.feature:83:5
      Matched: integration_tests/tests/steps/node_steps.rs:925:1
      Step panicked. Captured output: Node NODE2 only received 10 of 11 expected peers
      Client {
          base_nodes: {},
          blocks: {},
          miners: {},
          ffi_wallets: {},
          wallets: {},
          merge_mining_proxies: {},
          chat_clients: [],
          transactions: {},
          wallet_addresses: {},
          utxos: {},
          output_hash: None,
          pre_image: None,
          wallet_connected_to_base_node: {},
          seed_nodes: [
              "seed_node_0",
              "seed_node_1",
              "seed_node_2",
              "seed_node_3",
              "seed_node_4",
              "seed_node_5",
              "seed_node_6",
              "seed_node_7",
              "seed_node_8",
              "seed_node_9",
          ],
          wallet_tx_ids: {},
          errors: [],
          last_imported_tx_ids: [],
          last_merge_miner_response: Null,
      }

Check warning on line 0 in /

See this annotation in the file changed.

@github-actions github-actions / Test Results (Integration tests)

All 3 runs failed: Scenario: Syncing node while also mining before tip sync: tests/features/Sync.feature:142:5

artifacts/junit-cucumber/cucumber-output-junit.xml [took 26s]
Raw output
Step panicked. Captured output: Service on port 18286 never started
  Scenario Outline: Syncing node while also mining before tip sync
   ✔  Given I have a seed node SEED
   ✔  When I have wallet WALLET1 connected to seed node SEED
   ✔  When I have wallet WALLET2 connected to seed node SEED
   ✔  When I have mining node MINER connected to base node SEED and wallet WALLET1
   ✔  When I have a base node SYNCER connected to all seed nodes
   ✔  When I have mine-before-tip mining node MINER2 connected to base node SYNCER and wallet WALLET2
   ✔  When I stop node SYNCER
   ✔  When mining node MINER mines 101 blocks with min difficulty 1 and max difficulty 9999999999
   ✔  Then node SEED is at height 101
   ✘  When I start base node SYNCER
      Step failed:
      Defined: tests/features/Sync.feature:134:5
      Matched: integration_tests/tests/steps/node_steps.rs:68:1
      Step panicked. Captured output: Service on port 18286 never started
      Client {
          base_nodes: {},
          blocks: {},
          miners: {
              "MINER": MinerProcess {
                  name: "MINER",
                  base_node_name: "SEED",
                  wallet_name: "WALLET1",
                  mine_until_height: 100000,
                  stealth: false,
              },
              "MINER2": MinerProcess {
                  name: "MINER2",
                  base_node_name: "SYNCER",
                  wallet_name: "WALLET2",
                  mine_until_height: 100000,
                  stealth: false,
              },
          },
          ffi_wallets: {},
          wallets: {},
          merge_mining_proxies: {},
          chat_clients: [],
          transactions: {},
          wallet_addresses: {},
          utxos: {},
          output_hash: None,
          pre_image: None,
          wallet_connected_to_base_node: {
              "WALLET1": "SEED",
              "WALLET2": "SEED",
          },
          seed_nodes: [
              "SEED",
          ],
          wallet_tx_ids: {},
          errors: [],
          last_imported_tx_ids: [],
          last_merge_miner_response: Null,
      }

Check notice on line 0 in .github

See this annotation in the file changed.

@github-actions github-actions / Test Results (Integration tests)

33 tests found

There are 33 tests, see "Raw output" for the full list of tests.
Raw output
Scenario: A message is propagated between clients via 3rd party: tests/features/ChatFFI.feature:7:3
Scenario: A message is propagated between side loaded chat and client via 3rd party: tests/features/ChatFFI.feature:109:3
Scenario: A message receives a delivery receipt via FFI: tests/features/ChatFFI.feature:78:3
Scenario: A message receives a read receipt via FFI: tests/features/ChatFFI.feature:86:3
Scenario: As a client I want to receive a one-sided transaction: tests/features/WalletFFI.feature:212:5
Scenario: As a client I want to receive contact liveness events: tests/features/WalletFFI.feature:73:5
Scenario: As a client I want to retrieve a list of transactions I have made and received: tests/features/WalletFFI.feature:96:5
Scenario: As a client I want to retrieve the mnemonic word list for a given language: tests/features/WalletFFI.feature:24:5
Scenario: As a client I want to send a one-sided transaction: tests/features/WalletFFI.feature:175:5
Scenario: As a wallet I want to submit a transaction: tests/features/WalletQuery.feature:18:3
Scenario: As a wallet send to a wallet connected to a different base node: tests/features/WalletTransfer.feature:9:3
Scenario: Callback for delivery confirmation received: tests/features/ChatFFI.feature:22:3
Scenario: Callback for new message received: tests/features/ChatFFI.feature:14:3
Scenario: Callback for read confirmation received: tests/features/ChatFFI.feature:31:3
Scenario: Chat shuts down without any errors: tests/features/ChatFFI.feature:63:3
Scenario: Clear out mempool: tests/features/Mempool.feature:46:3
Scenario: Create burn transaction: tests/features/WalletTransactions.feature:411:3
Scenario: Fetches all addresses from FFI conversations: tests/features/ChatFFI.feature:95:3
Scenario: Node rolls back reorg on invalid block: tests/features/Reorgs.feature:63:3
Scenario: Reply to message: tests/features/ChatFFI.feature:68:3
Scenario: Simple block sync: tests/features/Sync.feature:26:3
Scenario: Simple propagation: tests/features/Propagation.feature:26:3
Scenario: Simple reorg to stronger chain: tests/features/Reorgs.feature:8:3
Scenario: Simple reorg with burned output: tests/features/Reorgs.feature:33:3
Scenario: Sync burned output: tests/features/Sync.feature:34:3
Scenario: Syncing node while also mining before tip sync: tests/features/Sync.feature:142:5
Scenario: Transactions are propagated through a network: tests/features/Mempool.feature:8:3
Scenario: Verify UTXO and kernel MMR size in header: tests/features/BlockTemplate.feature:8:1
Scenario: Verify gprc cna create block with more than 1 coinbase: tests/features/BlockTemplate.feature:14:5
Scenario: Wallet recovery with connected base node staying online: tests/features/WalletRecovery.feature:8:5
Scenario: Wallet sending and receiving one-sided transactions: tests/features/WalletTransactions.feature:8:3
Scenario: When a new node joins the network, it receives all peers: tests/features/Sync.feature:77:3
Scenario: Zero-conf transactions: tests/features/Mempool.feature:124:3