GitHub Actions / Test Results (Integration tests)
failed
Nov 10, 2023 in 0s.
View latest attempt.
6 fail, 25 pass in 16m 59s
Annotations
github-actions / Test Results (Integration tests)
All 3 runs failed: Scenario: A message is propagated between clients via 3rd party: tests/features/ChatFFI.feature:7:3
artifacts/junit-ffi-cucumber/cucumber-output-junit.xml [took 10s]
Raw output
Step panicked. Captured output: Service on port 18160 never started
Scenario: A message is propagated between clients via 3rd party
✘ Given I have a seed node SEED_A
Step failed:
Defined: tests/features/ChatFFI.feature:8:5
Matched: integration_tests/tests/steps/node_steps.rs:42:1
Step panicked. Captured output: Service on port 18160 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,
}
github-actions / Test Results (Integration tests)
All 3 runs failed: Scenario: Callback for new message received: tests/features/ChatFFI.feature:14:3
artifacts/junit-ffi-cucumber/cucumber-output-junit.xml [took 10s]
Raw output
Step panicked. Captured output: Service on port 18446 never started
Scenario: Callback for new message received
✘ Given I have a seed node SEED_A
Step failed:
Defined: tests/features/ChatFFI.feature:15:5
Matched: integration_tests/tests/steps/node_steps.rs:42:1
Step panicked. Captured output: Service on port 18446 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,
}
github-actions / Test Results (Integration tests)
All 3 runs failed: Scenario: Callback for delivery confirmation received: tests/features/ChatFFI.feature:22:3
artifacts/junit-ffi-cucumber/cucumber-output-junit.xml [took 10s]
Raw output
Step panicked. Captured output: Service on port 18378 never started
Scenario: Callback for delivery confirmation received
✘ Given I have a seed node SEED_A
Step failed:
Defined: tests/features/ChatFFI.feature:23:5
Matched: integration_tests/tests/steps/node_steps.rs:42:1
Step panicked. Captured output: Service on port 18378 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,
}
github-actions / Test Results (Integration tests)
All 3 runs failed: Scenario: Callback for read confirmation received: tests/features/ChatFFI.feature:31:3
artifacts/junit-ffi-cucumber/cucumber-output-junit.xml [took 10s]
Raw output
Step panicked. Captured output: Service on port 18091 never started
Scenario: Callback for read confirmation received
✘ Given I have a seed node SEED_A
Step failed:
Defined: tests/features/ChatFFI.feature:32:5
Matched: integration_tests/tests/steps/node_steps.rs:42:1
Step panicked. Captured output: Service on port 18091 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,
}
github-actions / Test Results (Integration tests)
1 out of 2 runs failed: Scenario: Chat shuts down without any errors: tests/features/ChatFFI.feature:63:3
artifacts/junit-ffi-cucumber/cucumber-output-junit.xml [took 10s]
Raw output
Step panicked. Captured output: Service on port 18494 never started
Scenario: Chat shuts down without any errors
✘ Given I have a seed node SEED_A
Step failed:
Defined: tests/features/ChatFFI.feature:64:5
Matched: integration_tests/tests/steps/node_steps.rs:42:1
Step panicked. Captured output: Service on port 18494 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,
}
github-actions / Test Results (Integration tests)
1 out of 2 runs failed: Scenario: Reply to message: tests/features/ChatFFI.feature:68:3
artifacts/junit-ffi-cucumber/cucumber-output-junit.xml [took 10s]
Raw output
Step panicked. Captured output: Service on port 18148 never started
Scenario: Reply to message
✘ Given I have a seed node SEED_A
Step failed:
Defined: tests/features/ChatFFI.feature:69:5
Matched: integration_tests/tests/steps/node_steps.rs:42:1
Step panicked. Captured output: Service on port 18148 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 notice on line 0 in .github
github-actions / Test Results (Integration tests)
31 tests found
There are 31 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 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