chore: new release v1.11.1-rc.0 #6776
Merged
GitHub Actions / Test Results (Integration tests)
failed
Jan 30, 2025 in 0s
1 fail, 35 pass in 43m 27s
2 files 11 suites 43m 27s ⏱️
36 tests 35 ✅ 0 💤 1 ❌
38 runs 36 ✅ 0 💤 2 ❌
Results for commit 32e685f.
Annotations
github-actions / Test Results (Integration tests)
2 out of 3 runs failed: Scenario: As a wallet send to a wallet connected to a different base node: tests/features/WalletTransfer.feature:9:3
artifacts/junit-cucumber/cucumber-output-junit.xml [took 9m 41s]
Raw output
Step panicked. Captured output: Wallet WALLET_B failed to have at least 5T, it ended with 0T
Scenario: As a wallet send to a wallet connected to a different base node
✔ Given I have a seed node SEED_A
✔ When I have a seed node SEED_B
✔ When I have a base node NODE_A connected to all seed nodes
✔ When I have a base node NODE_B connected to all seed nodes
✔ When I have wallet WALLET_A with 10T connected to base node NODE_A
✔ When I have wallet WALLET_B connected to base node NODE_B
✔ When I wait 5 seconds
✔ When I transfer 5T from WALLET_A to WALLET_B
✔ When I mine 4 blocks on SEED_A
✔ Then wallet WALLET_A has 5T
✔ When I wait 5 seconds
✘ When wallet WALLET_B has 5T
Step failed:
Defined: tests/features/WalletTransfer.feature:21:5
Matched: integration_tests/tests/steps/wallet_steps.rs:1537:1
Step panicked. Captured output: Wallet WALLET_B failed to have at least 5T, it ended with 0T
Client {
base_nodes: {},
blocks: {},
miners: {
"temp_miner": MinerProcess {
name: "temp_miner",
base_node_name: "NODE_A",
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_A",
"WALLET_B": "NODE_B",
},
seed_nodes: [
"SEED_A",
"SEED_B",
],
wallet_tx_ids: {
"H4EFNXrCypMDR8E64ikpb2afJBPrSoQEd1h2yPkNaW9yVBnS2wD9iewh8qkEhs8SLaU1ie8jzik9ys1aMP163SyPRuh": [
9726497111104486299,
],
"H4KkN1wZM82qaX68dwk3hS8GYv7csCQLyT7myHUnEjxUmiYUfgx8zvcDsRR8pa9Zuis3CZjnRc24CVTaU7JU8XDrbJP": [
9726497111104486299,
],
},
errors: [],
last_imported_tx_ids: [],
last_merge_miner_response: Null,
}
Check notice on line 0 in .github
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
Loading