Skip to content

fix unit test

Sign in for the full log view
GitHub Actions / Test Results (Integration tests) failed Oct 7, 2024 in 0s

3 fail, 33 pass in 34m 50s

 2 files  ±0  11 suites  ±0   34m 50s ⏱️ + 20m 3s
36 tests ±0  33 ✅  - 3  0 💤 ±0  3 ❌ +3 
39 runs  +3  36 ✅ ±0  0 💤 ±0  3 ❌ +3 

Results for commit 6ce3c38. ± Comparison against earlier commit ee9624a.

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: Create burn transaction: tests/features/WalletTransactions.feature:412:3 

artifacts/junit-cucumber/cucumber-output-junit.xml [took 2m 31s]
Raw output 
Step panicked. Captured output: Burn transaction has status 0 when we desired 1 (TRANSACTION_STATUS_BROADCAST), 2 (TRANSACTION_STATUS_UNCONFIRMED), or 6 (TRANSACTION_STATUS_CONFIRMED)
  Scenario: Create burn transaction
   ✔  Given I have a seed node NODE
   ✔  When I have 2 base nodes connected to all seed nodes
   ✔  When I have wallet WALLET_A connected to all seed nodes
   ✔  When I have wallet WALLET_B connected to all seed nodes
   ✔  When I have mining node MINER_A connected to base node NODE and wallet WALLET_A
   ✔  When I have mining node MINER_B connected to base node NODE and wallet WALLET_B
   ✔  When mining node MINER_A mines 12 blocks
   ✔  When mining node MINER_B mines 3 blocks
   ✔  Then all nodes are at height 15
   ✔  When I wait for wallet WALLET_A to have at least 221552530060 uT
   ✘  When I create a burn transaction of 201552500000 uT from WALLET_A at fee 100
      Step failed:
      Defined: tests/features/WalletTransactions.feature:423:5
      Matched: integration_tests/tests/steps/wallet_steps.rs:2785:1
      Step panicked. Captured output: Burn transaction has status 0 when we desired 1 (TRANSACTION_STATUS_BROADCAST), 2 (TRANSACTION_STATUS_UNCONFIRMED), or 6 (TRANSACTION_STATUS_CONFIRMED)
      Client {
          base_nodes: {},
          blocks: {},
          miners: {
              "MINER_A": MinerProcess {
                  name: "MINER_A",
                  base_node_name: "NODE",
                  wallet_name: "WALLET_A",
                  mine_until_height: 100000,
                  stealth: false,
              },
              "MINER_B": MinerProcess {
                  name: "MINER_B",
                  base_node_name: "NODE",
                  wallet_name: "WALLET_B",
                  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",
              "WALLET_B": "NODE",
          },
          seed_nodes: [
              "NODE",
          ],
          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)

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 8m 35s]
Raw output 
Step panicked. Captured output: Transaction from SENDER to FFI_WALLET with amount 2400000 at fee 5 failed to be broadcasted
  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 BASE1
   ✔  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
      Step failed:
      Defined: tests/features/WalletFFI.feature:191:9
      Matched: integration_tests/tests/steps/wallet_steps.rs:848:1
      Step panicked. Captured output: Transaction from SENDER to FFI_WALLET with amount 2400000 at fee 5 failed to be broadcasted
      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: 18334,
                  base_dir: "/runner/_work/tari/tari/integration_tests/tests/temp/cucumber_60121/Wallet FFI/As a client I want to send a one-sided transaction/ffi_wallets/FFI_WALLET_port_18334",
                  wallet: Mutex {
                      data: Wallet {
                          ptr: 0x00007f027807ecc0,
                          liveness_data: Mutex {
                              data: {
                                  "H4K5U2tngZeGrVpzDR42jhB2xqUbMhZaAn6FbS5baXPLVDmxsnWFp9XXsFkLPiKXrQDxQxdRPCRzkb8uny6HHSarmXa": ContactsLivenessData {
                                      ptr: 0x00007efc9c00a840,
                                  },
                                  "H47N939SfU5rDSfxiG6TGtFUvFQiHYRprVLewcBkvPDhL6nZfb3mdtFoCZKMj8g3a42aJaozodbgb6F7zgUBdzxC2xq": ContactsLivenessData {
                                      ptr: 0x00007f01400de750,
                                  },
                              },
                              poisoned: false,
                              ..
                          },
                          balance: CachedBalance {
                              available: 0,
                              time_locked: 0,
                              pending_incoming: 0,
                              pending_outgoing: 0,
                          },
                      },
                      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: {},
          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: As a client I want to receive a one-sided transaction: tests/features/WalletFFI.feature:212:5 

artifacts/junit-ffi-cucumber/cucumber-output-junit.xml [took 8m 38s]
Raw output 
Step panicked. Captured output: One sided transaction from SENDER to FFI_RECEIVER with amount 1000000 at fee 20 failed to be broadcasted
  Scenario: As a client I want to receive 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 a base node BASE2 connected to all seed nodes
   ✔  When I have wallet SENDER connected to base node BASE1
   ✔  And I have a ffi wallet FFI_RECEIVER connected to base node BASE2
   ✔  When I have mining node MINER connected to base node BASE1 and wallet SENDER
   ✔  When mining node MINER mines 10 blocks
   ✔  Then I wait for wallet SENDER to have at least 5000000 uT
   ✘  Then I send a one-sided transaction of 1000000 uT from SENDER to FFI_RECEIVER at fee 20
      Step failed:
      Defined: tests/features/WalletFFI.feature:221:9
      Matched: integration_tests/tests/steps/wallet_steps.rs:749:1
      Step panicked. Captured output: One sided transaction from SENDER to FFI_RECEIVER with amount 1000000 at fee 20 failed to be broadcasted
      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_RECEIVER": WalletFFI {
                  name: "FFI_RECEIVER",
                  port: 18362,
                  base_dir: "/runner/_work/tari/tari/integration_tests/tests/temp/cucumber_60121/Wallet FFI/As a client I want to receive a one-sided transaction/ffi_wallets/FFI_RECEIVER_port_18362",
                  wallet: Mutex {
                      data: Wallet {
                          ptr: 0x000055ad314dfa20,
                          liveness_data: Mutex {
                              data: {},
                              poisoned: false,
                              ..
                          },
                          balance: CachedBalance {
                              available: 0,
                              time_locked: 0,
                              pending_incoming: 0,
                              pending_outgoing: 0,
                          },
                      },
                      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",
          },
          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)

36 tests found 

There are 36 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:105:3
Scenario: A message is sent directly between two FFI clients: tests/features/ChatFFI.feature:49:3
Scenario: A message receives a delivery receipt via FFI: tests/features/ChatFFI.feature:74:3
Scenario: A message receives a read receipt via FFI: tests/features/ChatFFI.feature:82:3
Scenario: A single message is fetched from FFI: tests/features/ChatFFI.feature:113: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: Callback for status change is received: tests/features/ChatFFI.feature:41:3
Scenario: Chat shuts down without any errors: tests/features/ChatFFI.feature:59:3
Scenario: Clear out mempool: tests/features/Mempool.feature:46:3
Scenario: Create burn transaction: tests/features/WalletTransactions.feature:412:3
Scenario: Fetches all addresses from FFI conversations: tests/features/ChatFFI.feature:91:3
Scenario: Node rolls back reorg on invalid block: tests/features/Reorgs.feature:63:3
Scenario: Reply to message: tests/features/ChatFFI.feature:64: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: 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 can create block with more than 1 coinbase: tests/features/BlockTemplate.feature:14:5
Scenario: Wallet imports pre_mine UTXO: tests/features/WalletTransactions.feature:170:3
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
View more details on GitHub Actions