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: add configurable exclude dialer addresses for universe #6543

Merged

clippy

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

feat: add configurable exclude dialer addresses for universe #6543

clippy
21717d7
Select commit
Loading
Failed to load commit list.
GitHub Actions / Test Results (Integration tests) failed Sep 10, 2024 in 0s

2 fail, 34 pass in 39m 34s

 2 files  11 suites   39m 34s ⏱️
36 tests 34 ✅ 0 💤 2 ❌
38 runs  36 ✅ 0 💤 2 ❌

Results for commit 21717d7.

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: Simple propagation: tests/features/Propagation.feature:26:3

artifacts/junit-cucumber/cucumber-output-junit.xml [took 14m 24s]
Raw output
Step panicked. Captured output: base nodes not successfully synchronized at height 5, {"seed_node_0": 0, "seed_node_1": 0, "Node_0": 0, "Node_1": 0, "Node_2": 0, "Node_3": 0, "MINER": 5}
  Scenario: Simple propagation
   ✔  Given I have 2 seed nodes
   ✔  When I have 4 base nodes connected to all seed nodes
   ✔  When I have a SHA3 miner MINER connected to all seed nodes
   ✔  When mining node MINER mines 5 blocks
   ✔  Then node MINER is at height 5
   ✘  Then all nodes are at height 5
      Step failed:
      Defined: tests/features/Propagation.feature:32:5
      Matched: integration_tests/tests/steps/node_steps.rs:180:1
      Step panicked. Captured output: base nodes not successfully synchronized at height 5, {"seed_node_0": 0, "seed_node_1": 0, "Node_0": 0, "Node_1": 0, "Node_2": 0, "Node_3": 0, "MINER": 5}
      Client {
          base_nodes: {},
          blocks: {},
          miners: {
              "MINER": MinerProcess {
                  name: "MINER",
                  base_node_name: "MINER",
                  wallet_name: "MINER",
                  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: {},
          seed_nodes: [
              "seed_node_0",
              "seed_node_1",
          ],
          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: Wallet sending and receiving one-sided transactions: tests/features/WalletTransactions.feature:8:3

artifacts/junit-cucumber/cucumber-output-junit.xml [took 9m 27s]
Raw output
Step panicked. Captured output: One sided transaction from WALLET_B to WALLET_C with amount 1500000 at fee 20 failed to be broadcasted
  Scenario: Wallet sending and receiving one-sided transactions
   ✔  Given I have a seed node NODE
   ✔  When I have 1 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 wallet WALLET_C connected to all seed nodes
   ✔  When I have mining node MINER connected to base node NODE and wallet WALLET_A
   ✔  When mining node MINER mines 15 blocks
   ✔  Then all nodes are at height 15
   ✔  When I wait 5 seconds
   ✔  When I wait for wallet WALLET_A to have at least 55000000000 uT
   ✔  Then I send a one-sided transaction of 1000000 uT from WALLET_A to WALLET_B at fee 100
   ✔  Then I send a one-sided transaction of 1000000 uT from WALLET_A to WALLET_B at fee 100
   ✔  When mining node MINER mines 5 blocks
   ✔  Then all nodes are at height 20
   ✔  Then I wait for wallet WALLET_B to have at least 2000000 uT
   ✔  Then I send 900000 uT from wallet WALLET_B to wallet WALLET_B at fee 20
   ✔  Then I wait for wallet WALLET_B to have less than 1100000 uT
   ✔  When mining node MINER mines 5 blocks
   ✔  Then all nodes are at height 25
   ✔  Then I wait for wallet WALLET_B to have at least 1900000 uT
   ✘  Then I send a one-sided transaction of 1500000 uT from WALLET_B to WALLET_C at fee 20
      Step failed:
      Defined: tests/features/WalletTransactions.feature:31:5
      Matched: integration_tests/tests/steps/wallet_steps.rs:749:1
      Step panicked. Captured output: One sided transaction from WALLET_B to WALLET_C with amount 1500000 at fee 20 failed to be broadcasted
      Client {
          base_nodes: {},
          blocks: {},
          miners: {
              "MINER": MinerProcess {
                  name: "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",
              "WALLET_B": "NODE",
              "WALLET_C": "NODE",
          },
          seed_nodes: [
              "NODE",
          ],
          wallet_tx_ids: {
              "H4CJxybv7Ddbcp3fkZ2k2Zgxwi3LVx3TTqexRKyLq5ENft9t9PF23sfZ5nKWVamw8iPwbGvEANd5QsuEPtNd1EDHz9A": [
                  15522728221995683,
                  10379895404926089747,
              ],
              "H46VSRg7YKbzTPKGiThseUWvyHoBHEPaj4F6PgpN27RTVuCP2XG1zq8RViXskYCMw1UiMwkrGbSv2pY85KHERKFtGvC": [
                  15522728221995683,
                  10379895404926089747,
                  6036457482594152793,
                  6036457482594152793,
              ],
          },
          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