Skip to content

chore: improve wallet recovery log message (#6792) #1827

chore: improve wallet recovery log message (#6792)

chore: improve wallet recovery log message (#6792) #1827

GitHub Actions / JUnit Test Report failed Feb 7, 2025 in 0s

40 tests run, 35 passed, 0 skipped, 5 failed.

Annotations

Check failure on line 1 in feature:33:3

See this annotation in the file changed.

@github-actions github-actions / JUnit Test Report

feature:33:3.Scenario: Simple reorg with burned output: tests/features/Reorgs.feature:33:3

Step panicked. Captured output: base node didn't synchronize successfully with height 17, current chain height 15
Raw output
Scenario: Simple reorg with burned output
     Given I have a seed node SEED_B
     When I have a base node B connected to seed SEED_B
     When I have wallet WB connected to base node B
     When I have mining node BM connected to base node B and wallet WB
     When mining node BM mines 10 blocks with min difficulty 1 and max difficulty 1
     When I wait for wallet WB to have at least 55000000000 uT
     When I create a burn transaction of 1000000 uT from WB at fee 100
     When mining node BM mines 5 blocks with min difficulty 1 and max difficulty 1
     Given I have a seed node SEED_C
     When I have a base node C connected to seed SEED_C
     When I have wallet WC connected to base node C
     When I have mining node CM connected to base node C and wallet WC
     When mining node CM mines 17 blocks with min difficulty 1 and max difficulty 1
     Then node B is at height 15
     Then node C is at height 17
     When I have a base node SA connected to nodes B,C
     Then node SA is at height 17
     Then node B is at height 17
      Step failed:
      Defined: tests/features/Reorgs.feature:59:5
      Matched: integration_tests/tests/steps/node_steps.rs:218:1
      Step panicked. Captured output: base node didn't synchronize successfully with height 17, current chain height 15
      Client {
          base_nodes: {},
          blocks: {},
          miners: {
              "BM": MinerProcess {
                  name: "BM",
                  base_node_name: "B",
                  wallet_name: "WB",
                  mine_until_height: 100000,
                  stealth: false,
              },
              "CM": MinerProcess {
                  name: "CM",
                  base_node_name: "C",
                  wallet_name: "WC",
                  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: {
              "WB": "B",
              "WC": "C",
          },
          seed_nodes: [
              "SEED_B",
              "SEED_C",
          ],
          wallet_tx_ids: {},
          errors: [],
          last_imported_tx_ids: [],
          last_merge_miner_response: Null,
      }

Check failure on line 1 in feature:33:3

See this annotation in the file changed.

@github-actions github-actions / JUnit Test Report

feature:33:3.Scenario: Simple reorg with burned output: tests/features/Reorgs.feature:33:3

Step panicked. Captured output: base node didn't synchronize successfully with height 17, current chain height 15
Raw output
Scenario: Simple reorg with burned output | Retry attempt: 1/2
     Given I have a seed node SEED_B
     When I have a base node B connected to seed SEED_B
     When I have wallet WB connected to base node B
     When I have mining node BM connected to base node B and wallet WB
     When mining node BM mines 10 blocks with min difficulty 1 and max difficulty 1
     When I wait for wallet WB to have at least 55000000000 uT
     When I create a burn transaction of 1000000 uT from WB at fee 100
     When mining node BM mines 5 blocks with min difficulty 1 and max difficulty 1
     Given I have a seed node SEED_C
     When I have a base node C connected to seed SEED_C
     When I have wallet WC connected to base node C
     When I have mining node CM connected to base node C and wallet WC
     When mining node CM mines 17 blocks with min difficulty 1 and max difficulty 1
     Then node B is at height 15
     Then node C is at height 17
     When I have a base node SA connected to nodes B,C
     Then node SA is at height 17
     Then node B is at height 17
      Step failed:
      Defined: tests/features/Reorgs.feature:59:5
      Matched: integration_tests/tests/steps/node_steps.rs:218:1
      Step panicked. Captured output: base node didn't synchronize successfully with height 17, current chain height 15
      Client {
          base_nodes: {},
          blocks: {},
          miners: {
              "BM": MinerProcess {
                  name: "BM",
                  base_node_name: "B",
                  wallet_name: "WB",
                  mine_until_height: 100000,
                  stealth: false,
              },
              "CM": MinerProcess {
                  name: "CM",
                  base_node_name: "C",
                  wallet_name: "WC",
                  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: {
              "WB": "B",
              "WC": "C",
          },
          seed_nodes: [
              "SEED_B",
              "SEED_C",
          ],
          wallet_tx_ids: {},
          errors: [],
          last_imported_tx_ids: [],
          last_merge_miner_response: Null,
      }

Check failure on line 1 in feature:33:3

See this annotation in the file changed.

@github-actions github-actions / JUnit Test Report

feature:33:3.Scenario: Simple reorg with burned output: tests/features/Reorgs.feature:33:3

Step panicked. Captured output: base node didn't synchronize successfully with height 17, current chain height 15
Raw output
Scenario: Simple reorg with burned output | Retry attempt: 2/2
     Given I have a seed node SEED_B
     When I have a base node B connected to seed SEED_B
     When I have wallet WB connected to base node B
     When I have mining node BM connected to base node B and wallet WB
     When mining node BM mines 10 blocks with min difficulty 1 and max difficulty 1
     When I wait for wallet WB to have at least 55000000000 uT
     When I create a burn transaction of 1000000 uT from WB at fee 100
     When mining node BM mines 5 blocks with min difficulty 1 and max difficulty 1
     Given I have a seed node SEED_C
     When I have a base node C connected to seed SEED_C
     When I have wallet WC connected to base node C
     When I have mining node CM connected to base node C and wallet WC
     When mining node CM mines 17 blocks with min difficulty 1 and max difficulty 1
     Then node B is at height 15
     Then node C is at height 17
     When I have a base node SA connected to nodes B,C
     Then node SA is at height 17
     Then node B is at height 17
      Step failed:
      Defined: tests/features/Reorgs.feature:59:5
      Matched: integration_tests/tests/steps/node_steps.rs:218:1
      Step panicked. Captured output: base node didn't synchronize successfully with height 17, current chain height 15
      Client {
          base_nodes: {},
          blocks: {},
          miners: {
              "BM": MinerProcess {
                  name: "BM",
                  base_node_name: "B",
                  wallet_name: "WB",
                  mine_until_height: 100000,
                  stealth: false,
              },
              "CM": MinerProcess {
                  name: "CM",
                  base_node_name: "C",
                  wallet_name: "WC",
                  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: {
              "WB": "B",
              "WC": "C",
          },
          seed_nodes: [
              "SEED_B",
              "SEED_C",
          ],
          wallet_tx_ids: {},
          errors: [],
          last_imported_tx_ids: [],
          last_merge_miner_response: Null,
      }

Check failure on line 1 in feature:9:3

See this annotation in the file changed.

@github-actions github-actions / JUnit Test Report

feature:9:3.Scenario: As a wallet send to a wallet connected to a different base node: tests/features/WalletTransfer.feature:9:3

Step panicked. Captured output: Wallet WALLET_B failed to have at least 5T, it ended with 0T
Raw output
Scenario: As a wallet send to a wallet connected to a different base node
     Given I have a seed node SEED_A
     When I have a seed node SEED_B
     When I have a base node NODE_A connected to all seed nodes
     When I have a base node NODE_B connected to all seed nodes
     When I have wallet WALLET_A with 10T connected to base node NODE_A
     When I have wallet WALLET_B connected to base node NODE_B
     When I wait 5 seconds
     When I transfer 5T from WALLET_A to WALLET_B
     When I mine 4 blocks on SEED_A
     Then wallet WALLET_A has 5T
     When I wait 5 seconds
     When wallet WALLET_B has 5T
      Step failed:
      Defined: tests/features/WalletTransfer.feature:21:5
      Matched: integration_tests/tests/steps/wallet_steps.rs:1537:1
      Step panicked. Captured output: Wallet WALLET_B failed to have at least 5T, it ended with 0T
      Client {
          base_nodes: {},
          blocks: {},
          miners: {
              "temp_miner": MinerProcess {
                  name: "temp_miner",
                  base_node_name: "NODE_A",
                  wallet_name: "WALLET_A",
                  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: {
              "WALLET_A": "NODE_A",
              "WALLET_B": "NODE_B",
          },
          seed_nodes: [
              "SEED_A",
              "SEED_B",
          ],
          wallet_tx_ids: {
              "H46t7dCxQLJBiuTsoXy9H6hs5mUWJtj52SH1sbHogna3ibzhXtX9zgwGavjG9cTQgRKsN9Xb2PTtKe6TbFG4jf4jAUf": [
                  4874219633977690296,
              ],
              "H487iwyC73FyaGC26rdrcWNYTb3baY7E4Q8UrRyekTNurjkCTynL9V85cbNjQEiay6zvxk1Cfsks56HAx4JXJt4ERzk": [
                  4874219633977690296,
              ],
          },
          errors: [],
          last_imported_tx_ids: [],
          last_merge_miner_response: Null,
      }

Check failure on line 1 in feature:9:3

See this annotation in the file changed.

@github-actions github-actions / JUnit Test Report

feature:9:3.Scenario: As a wallet send to a wallet connected to a different base node: tests/features/WalletTransfer.feature:9:3

Step panicked. Captured output: Wallet WALLET_B failed to have at least 5T, it ended with 0T
Raw output
Scenario: As a wallet send to a wallet connected to a different base node | Retry attempt: 1/2
     Given I have a seed node SEED_A
     When I have a seed node SEED_B
     When I have a base node NODE_A connected to all seed nodes
     When I have a base node NODE_B connected to all seed nodes
     When I have wallet WALLET_A with 10T connected to base node NODE_A
     When I have wallet WALLET_B connected to base node NODE_B
     When I wait 5 seconds
     When I transfer 5T from WALLET_A to WALLET_B
     When I mine 4 blocks on SEED_A
     Then wallet WALLET_A has 5T
     When I wait 5 seconds
     When wallet WALLET_B has 5T
      Step failed:
      Defined: tests/features/WalletTransfer.feature:21:5
      Matched: integration_tests/tests/steps/wallet_steps.rs:1537:1
      Step panicked. Captured output: Wallet WALLET_B failed to have at least 5T, it ended with 0T
      Client {
          base_nodes: {},
          blocks: {},
          miners: {
              "temp_miner": MinerProcess {
                  name: "temp_miner",
                  base_node_name: "NODE_A",
                  wallet_name: "WALLET_A",
                  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: {
              "WALLET_A": "NODE_A",
              "WALLET_B": "NODE_B",
          },
          seed_nodes: [
              "SEED_A",
              "SEED_B",
          ],
          wallet_tx_ids: {
              "H4P7DaaePQGg2mNnYA5r2o1zDdCVccS78Xx8RNuzLAihUKQvr2yFVPScMfCYJoW5mNfDBHxMswt94PRRmBA4QrHUFjh": [
                  10520620952272110044,
              ],
              "H4R5aeZJKuvQgdSCSRyE8Fo4vaWZ9ayhFJFXWrgDPXpcXoA3aoGRamXyW91ANAZhCQptACeugJbeCwRvFhXd5iq6ga": [
                  10520620952272110044,
              ],
          },
          errors: [],
          last_imported_tx_ids: [],
          last_merge_miner_response: Null,
      }