Skip to content

feat: split message to have dedicated to and from fields #4495

feat: split message to have dedicated to and from fields

feat: split message to have dedicated to and from fields #4495

GitHub Actions / Test Results (Integration tests) failed May 27, 2024 in 0s

1 parse errors, 6 fail, 12 pass in 12m 12s

 2 files   1 errors  9 suites   12m 12s ⏱️
18 tests 12 ✅ 0 💤  6 ❌
29 runs  18 ✅ 0 💤 11 ❌

Results for commit ceccdf9.

Annotations

Check failure on line 0 in artifacts/junit-ffi-cucumber/cucumber-output-junit.xml

See this annotation in the file changed.

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

Error processing result file

File is empty.
Raw output
artifacts/junit-ffi-cucumber/cucumber-output-junit.xml

Check warning on line 0 in /

See this annotation in the file changed.

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

2 out of 3 runs failed: Scenario: Verify UTXO and kernel MMR size in header: tests/features/BlockTemplate.feature:8:1

artifacts/junit-cucumber/cucumber-output-junit.xml [took 10s]
Raw output
Step panicked. Captured output: Service on port 18008 never started
  Scenario: Verify UTXO and kernel MMR size in header
   ✘  Given I have a seed node SEED_A
      Step failed:
      Defined: tests/features/BlockTemplate.feature:9:5
      Matched: integration_tests/tests/steps/node_steps.rs:56:1
      Step panicked. Captured output: Service on port 18008 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",
          ],
          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)

2 out of 3 runs failed: Scenario: Verify gprc cna create block with more than 1 coinbase: tests/features/BlockTemplate.feature:14:5

artifacts/junit-cucumber/cucumber-output-junit.xml [took 10s]
Raw output
Step panicked. Captured output: Service on port 18371 never started
  Scenario: Verify gprc cna create block with more than 1 coinbase
   ✘  Given I have a seed node SEED_A
      Step failed:
      Defined: tests/features/BlockTemplate.feature:15:9
      Matched: integration_tests/tests/steps/node_steps.rs:56:1
      Step panicked. Captured output: Service on port 18371 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",
          ],
          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)

2 out of 3 runs failed: Scenario: Transactions are propagated through a network: tests/features/Mempool.feature:8:3

artifacts/junit-cucumber/cucumber-output-junit.xml [took 10s]
Raw output
Step panicked. Captured output: Service on port 18325 never started
  Scenario: Transactions are propagated through a network
   ✘  Given I have 8 seed nodes
      Step failed:
      Defined: tests/features/Mempool.feature:13:5
      Matched: integration_tests/tests/steps/node_steps.rs:275:1
      Step panicked. Captured output: Service on port 18325 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_node_0",
          ],
          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)

2 out of 3 runs failed: Scenario: Clear out mempool: tests/features/Mempool.feature:46:3

artifacts/junit-cucumber/cucumber-output-junit.xml [took 10s]
Raw output
Step panicked. Captured output: Service on port 18314 never started
  Scenario: Clear out mempool
   ✘  Given I have 1 seed nodes
      Step failed:
      Defined: tests/features/Mempool.feature:47:5
      Matched: integration_tests/tests/steps/node_steps.rs:275:1
      Step panicked. Captured output: Service on port 18314 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_node_0",
          ],
          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)

2 out of 3 runs failed: Scenario: Zero-conf transactions: tests/features/Mempool.feature:124:3

artifacts/junit-cucumber/cucumber-output-junit.xml [took 10s]
Raw output
Step panicked. Captured output: Service on port 18038 never started
  Scenario: Zero-conf transactions
   ✘  Given I have 1 seed nodes
      Step failed:
      Defined: tests/features/Mempool.feature:125:5
      Matched: integration_tests/tests/steps/node_steps.rs:275:1
      Step panicked. Captured output: Service on port 18038 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_node_0",
          ],
          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: Syncing node while also mining before tip sync: tests/features/Sync.feature:142:5

artifacts/junit-cucumber/cucumber-output-junit.xml [took 26s]
Raw output
Step panicked. Captured output: Service on port 18404 never started
  Scenario Outline: Syncing node while also mining before tip sync
   ✔  Given I have a seed node SEED
   ✔  When I have wallet WALLET1 connected to seed node SEED
   ✔  When I have wallet WALLET2 connected to seed node SEED
   ✔  When I have mining node MINER connected to base node SEED and wallet WALLET1
   ✔  When I have a base node SYNCER connected to all seed nodes
   ✔  When I have mine-before-tip mining node MINER2 connected to base node SYNCER and wallet WALLET2
   ✔  When I stop node SYNCER
   ✔  When mining node MINER mines 101 blocks with min difficulty 1 and max difficulty 9999999999
   ✔  Then node SEED is at height 101
   ✘  When I start base node SYNCER
      Step failed:
      Defined: tests/features/Sync.feature:134:5
      Matched: integration_tests/tests/steps/node_steps.rs:68:1
      Step panicked. Captured output: Service on port 18404 never started
      Client {
          base_nodes: {},
          blocks: {},
          miners: {
              "MINER": MinerProcess {
                  name: "MINER",
                  base_node_name: "SEED",
                  wallet_name: "WALLET1",
                  mine_until_height: 100000,
                  stealth: false,
              },
              "MINER2": MinerProcess {
                  name: "MINER2",
                  base_node_name: "SYNCER",
                  wallet_name: "WALLET2",
                  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: {
              "WALLET1": "SEED",
              "WALLET2": "SEED",
          },
          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)

18 tests found

There are 18 tests, see "Raw output" for the full list of tests.
Raw output
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: Clear out mempool: tests/features/Mempool.feature:46:3
Scenario: Create burn transaction: tests/features/WalletTransactions.feature:411:3
Scenario: Node rolls back reorg on invalid block: tests/features/Reorgs.feature:63: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: Verify gprc cna create block with more than 1 coinbase: tests/features/BlockTemplate.feature:14:5
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