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 multiaddr with range checks for use with universe #6557

Merged

review comments

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

feat!: add multiaddr with range checks for use with universe #6557

review comments
0fbfdf4
Select commit
Loading
Failed to load commit list.
GitHub Actions / Test Results (Integration tests) failed Sep 17, 2024 in 0s

2 fail, 34 pass in 19m 37s

 2 files  ±0  11 suites  ±0   19m 37s ⏱️ + 4m 41s
36 tests ±0  34 ✅  - 2  0 💤 ±0  2 ❌ +2 
38 runs  +2  36 ✅ ±0  0 💤 ±0  2 ❌ +2 

Results for commit 0fbfdf4. ± Comparison against earlier commit 9d5874d.

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 reorg with burned output: tests/features/Reorgs.feature:33:3

artifacts/junit-cucumber/cucumber-output-junit.xml [took 2m 23s]
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: 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
      Step failed:
      Defined: tests/features/Reorgs.feature:43: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: {
              "BM": MinerProcess {
                  name: "BM",
                  base_node_name: "B",
                  wallet_name: "WB",
                  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",
          },
          seed_nodes: [
              "SEED_B",
          ],
          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: When a new node joins the network, it receives all peers: tests/features/Sync.feature:77:3

artifacts/junit-cucumber/cucumber-output-junit.xml [took 1m 44s]
Raw output
Step panicked. Captured output: Peer was not connected in time, connected to 9 peers
  Scenario: When a new node joins the network, it receives all peers
   ✔  Given I have 10 seed nodes
   ✔  When I have a base node NODE1 connected to all seed nodes
   ✘  When I wait for NODE1 to have 10 connections
      Step failed:
      Defined: tests/features/Sync.feature:80:5
      Matched: integration_tests/tests/steps/node_steps.rs:122:1
      Step panicked. Captured output: Peer was not connected in time, connected to 9 peers
      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_node_0",
              "seed_node_1",
              "seed_node_2",
              "seed_node_3",
              "seed_node_4",
              "seed_node_5",
              "seed_node_6",
              "seed_node_7",
              "seed_node_8",
              "seed_node_9",
          ],
          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