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 use transaction output as provided with encumber_aggregate_utxo #6594

Merged

review comments

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

feat: add use transaction output as provided with encumber_aggregate_utxo #6594

review comments
3cbd102
Select commit
Loading
Failed to load commit list.
GitHub Actions / Test Results (Integration tests) failed Oct 2, 2024 in 0s

1 parse errors, 1 fail, 17 pass in 13m 50s

 2 files  ± 0   1 errors  2 suites   - 9   13m 50s ⏱️ - 1m 52s
18 tests  - 18  17 ✅  - 19  0 💤 ±0  1 ❌ +1 
19 runs   - 17  18 ✅  - 18  0 💤 ±0  1 ❌ +1 

Results for commit 3cbd102. ± Comparison against earlier commit 2ed4203.

Annotations

Check failure on line 0 in artifacts/junit-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-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)

1 out of 2 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 8m 39s]
Raw output
Step panicked. Captured output: One sided transaction from SENDER to FFI_RECEIVER with amount 1000000 at fee 20 failed to be broadcasted
  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
      Step failed:
      Defined: tests/features/WalletFFI.feature:221:9
      Matched: integration_tests/tests/steps/wallet_steps.rs:749:1
      Step panicked. Captured output: One sided transaction from SENDER to FFI_RECEIVER with amount 1000000 at fee 20 failed to be broadcasted
      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: 18306,
                  base_dir: "/runner/_work/tari/tari/integration_tests/tests/temp/cucumber_12885/Wallet FFI/As a client I want to receive a one-sided transaction/ffi_wallets/FFI_RECEIVER_port_18306",
                  wallet: Mutex {
                      data: Wallet {
                          ptr: 0x0000556cded25580,
                          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: {},
          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: 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: 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: Fetches all addresses from FFI conversations: tests/features/ChatFFI.feature:91:3
Scenario: Reply to message: tests/features/ChatFFI.feature:64:3