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

chore: remove ahash as dependancy #6238

Merged
merged 1 commit into from
Mar 27, 2024

remove ahash as dependancy

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

chore: remove ahash as dependancy #6238

remove ahash as dependancy
83bf76d
Select commit
Loading
Failed to load commit list.
GitHub Actions / Test Results (Integration tests) failed Mar 26, 2024 in 0s

1 fail, 31 pass in 44m 41s

 2 files  11 suites   44m 41s ⏱️
32 tests 31 ✅ 0 💤 1 ❌
34 runs  32 ✅ 0 💤 2 ❌

Results for commit 83bf76d.

Annotations

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: 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 14m 28s]
Raw output
Step panicked. Captured output: base nodes not successfully synchronized at height 12, {"SEED": 12, "BASE1": 12, "BASE2": 0}
  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
   ✔  When mining node MINER mines 2 blocks
   ✘  Then all nodes are at height 12
      Step failed:
      Defined: tests/features/WalletFFI.feature:223:9
      Matched: integration_tests/tests/steps/node_steps.rs:166:1
      Step panicked. Captured output: base nodes not successfully synchronized at height 12, {"SEED": 12, "BASE1": 12, "BASE2": 0}
      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: 18091,
                  base_dir: "/runner/_work/tari/tari/integration_tests/tests/temp/cucumber_7173/Wallet FFI/As a client I want to receive a one-sided transaction/ffi_wallets/FFI_RECEIVER_port_18091",
                  wallet: Mutex {
                      data: Wallet {
                          ptr: 0x0000555fef8b2440,
                          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: {
              "08daaa1505fa5ce3d4e54942b60da601f86a482317df9c5f774669af3f96851bd7": [
                  5342298310504937936,
              ],
              "1097e19a7930f0f0294ea2bd3de021e210e2a6a8f20d7dc3748de6a8656b8b7af5": [
                  5342298310504937936,
              ],
          },
          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)

32 tests found

There are 32 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 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: 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