Skip to content

new esme release

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

1 fail, 28 pass in 14m 21s

 2 files  11 suites   14m 21s ⏱️
29 tests 28 ✅ 0 💤 1 ❌
31 runs  28 ✅ 0 💤 3 ❌

Results for commit 1260102.

Annotations

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

artifacts/junit-cucumber/cucumber-output-junit.xml [took 1m 3s]
Raw output 
Step panicked. Captured output: Wallet WALLET_A failed to detect tx with tx_id = 15312542179252048744 to be Mined_or_Faux_Confirmed, current status is Broadcast
  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
   ✔  When mining node MINER_B mines 5 blocks
   ✔  Then all nodes are at height 20
   ✘  Then wallet WALLET_A detects all transactions as Mined_or_Faux_Confirmed
      Step failed:
      Defined: tests/features/WalletTransactions.feature:425:5
      Matched: integration_tests/tests/steps/wallet_steps.rs:155:1
      Step panicked. Captured output: Wallet WALLET_A failed to detect tx with tx_id = 15312542179252048744 to be Mined_or_Faux_Confirmed, current status is Broadcast
      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 notice on line 0 in .github

See this annotation in the file changed.

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

29 tests found 

There are 29 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 contact liveness events: tests/features/WalletFFI.feature:73: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 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: 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