Skip to content

feat: check chain metadata (#6146) #1402

feat: check chain metadata (#6146)

feat: check chain metadata (#6146) #1402

GitHub Actions / JUnit Test Report failed Feb 19, 2024 in 0s

33 tests run, 29 passed, 0 skipped, 4 failed.

Annotations

Check failure on line 1 in feature:18:3

See this annotation in the file changed.

@github-actions github-actions / JUnit Test Report

feature:18:3.Scenario: As a wallet I want to submit a transaction: tests/features/WalletQuery.feature:18:3

Step panicked. Captured output: Wallet WALLET_A failed to have at least 10T
Raw output
Scenario: As a wallet I want to submit a transaction
     Given I have a seed node NODE
     When I have 1 base nodes connected to all seed nodes
     When I have wallet WALLET_A with 10T connected to base node NODE
      Step failed:
      Defined: tests/features/WalletQuery.feature:21:5
      Matched: integration_tests/tests/steps/wallet_steps.rs:1528:1
      Step panicked. Captured output: Wallet WALLET_A failed to have at least 10T
      Client {
          base_nodes: {},
          blocks: {},
          miners: {
              "temp_miner": MinerProcess {
                  name: "temp_miner",
                  base_node_name: "NODE",
                  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",
          },
          seed_nodes: [
              "NODE",
          ],
          wallet_tx_ids: {},
          errors: [],
          last_imported_tx_ids: [],
          last_merge_miner_response: Null,
      }

Check failure on line 1 in feature:8:5

See this annotation in the file changed.

@github-actions github-actions / JUnit Test Report

feature:8:5.Scenario: Wallet recovery with connected base node staying online: tests/features/WalletRecovery.feature:8:5

Step panicked. Captured output: Service on port 18357 never started
Raw output
Scenario: Wallet recovery with connected base node staying online
     Given I have a seed node NODE
     When I have wallet WALLET_A connected to all seed nodes
      Step failed:
      Defined: tests/features/WalletRecovery.feature:11:7
      Matched: integration_tests/tests/steps/wallet_steps.rs:84:1
      Step panicked. Captured output: Service on port 18357 never started
      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: {
              "WALLET_A": "NODE",
          },
          seed_nodes: [
              "NODE",
          ],
          wallet_tx_ids: {},
          errors: [],
          last_imported_tx_ids: [],
          last_merge_miner_response: Null,
      }

Check failure on line 1 in feature:411:3

See this annotation in the file changed.

@github-actions github-actions / JUnit Test Report

feature:411:3.Scenario: Create burn transaction: tests/features/WalletTransactions.feature:411:3

Step panicked. Captured output: Service on port 18402 never started
Raw output
Scenario: Create burn transaction
     Given I have a seed node NODE
      Step failed:
      Defined: tests/features/WalletTransactions.feature:412:5
      Matched: integration_tests/tests/steps/node_steps.rs:42:1
      Step panicked. Captured output: Service on port 18402 never started
      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: [
              "NODE",
          ],
          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: Service on port 18330 never started
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
      Step failed:
      Defined: tests/features/WalletTransfer.feature:12:5
      Matched: integration_tests/tests/steps/node_steps.rs:49:1
      Step panicked. Captured output: Service on port 18330 never started
      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_A",
              "SEED_B",
          ],
          wallet_tx_ids: {},
          errors: [],
          last_imported_tx_ids: [],
          last_merge_miner_response: Null,
      }