chore: upgrade prost and tonic (ring dep) #6603
Merged
GitHub Actions / Test Results (Integration tests)
failed
Oct 4, 2024 in 0s
1 fail, 35 pass in 17m 15s
2 files 11 suites 17m 15s ⏱️
36 tests 35 ✅ 0 💤 1 ❌
37 runs 36 ✅ 0 💤 1 ❌
Results for commit 827fc40.
Annotations
github-actions / Test Results (Integration tests)
1 out of 2 runs failed: Scenario: A message is sent directly between two FFI clients: tests/features/ChatFFI.feature:49:3
artifacts/junit-ffi-cucumber/cucumber-output-junit.xml [took 2m 31s]
Raw output
Step panicked. Captured output: Contact \U0001f339\U0001f308\U0001f3ae\U0001f45f\U0001f357\U0001f3a4\U0001f3e6\U0001f6a2\U0001f914\U0001f490\U0001f35f\U0001f6ab\U0001f607\U0001f4df\U0001f50b\U0001f344\U0001f43e\U0001f981\U0001f3a9\U0001f37a\U0001f411\U0001f363\U0001f4c8\U0001f423\U0001f383\U0001f4b5\U0001f4ff\U0001f344\U0001f30a\U0001f691\U0001f380\U0001f40b\U0001f442\U0001f41d\U0001f48e never came online, status is: NeverSeen
Scenario: A message is sent directly between two FFI clients
✔ Given I have a seed node SEED_A
✔ When I have a chat FFI client CHAT_A connected to seed node SEED_A
✔ When I have a chat FFI client CHAT_B connected to seed node SEED_A
✔ When CHAT_A adds CHAT_B as a contact
✔ When CHAT_B adds CHAT_A as a contact
✘ When CHAT_A waits for contact CHAT_B to be online
Step failed:
Defined: tests/features/ChatFFI.feature:55:5
Matched: integration_tests/tests/steps/chat_steps.rs:167:1
Step panicked. Captured output: Contact \U0001f339\U0001f308\U0001f3ae\U0001f45f\U0001f357\U0001f3a4\U0001f3e6\U0001f6a2\U0001f914\U0001f490\U0001f35f\U0001f6ab\U0001f607\U0001f4df\U0001f50b\U0001f344\U0001f43e\U0001f981\U0001f3a9\U0001f37a\U0001f411\U0001f363\U0001f4c8\U0001f423\U0001f383\U0001f4b5\U0001f4ff\U0001f344\U0001f30a\U0001f691\U0001f380\U0001f40b\U0001f442\U0001f41d\U0001f48e never came online, status is: NeverSeen
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 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