ci(feature): add quay expire for none release docker images
GitHub Actions / Test Results (Integration tests)
failed
Sep 9, 2024 in 0s
1 fail, 35 pass in 29m 12s
2 files 11 suites 29m 12s ⏱️
36 tests 35 ✅ 0 💤 1 ❌
37 runs 36 ✅ 0 💤 1 ❌
Results for commit 1f10663.
Annotations
github-actions / Test Results (Integration tests)
1 out of 2 runs failed: Scenario: Transactions are propagated through a network: tests/features/Mempool.feature:8:3
artifacts/junit-cucumber/cucumber-output-junit.xml [took 14m 15s]
Raw output
Step panicked. Captured output: base nodes not successfully synchronized at height 3, {"seed_node_0": 3, "seed_node_1": 3, "seed_node_2": 3, "seed_node_3": 0, "seed_node_4": 3, "seed_node_5": 3, "seed_node_6": 3, "seed_node_7": 3, "SENDER": 3, "Node_0": 3, "Node_1": 3, "Node_2": 3, "Node_3": 3, "Node_4": 3, "Node_5": 3, "Node_6": 3, "Node_7": 3}
Scenario: Transactions are propagated through a network
✔ Given I have 8 seed nodes
✔ When I have a base node SENDER connected to all seed nodes
✔ When I have 8 base nodes connected to all seed nodes
✔ When I mine a block on SENDER with coinbase CB1
✔ When I mine 2 blocks on SENDER
✘ Then all nodes are at height 3
Step failed:
Defined: tests/features/Mempool.feature:18:5
Matched: integration_tests/tests/steps/node_steps.rs:180:1
Step panicked. Captured output: base nodes not successfully synchronized at height 3, {"seed_node_0": 3, "seed_node_1": 3, "seed_node_2": 3, "seed_node_3": 0, "seed_node_4": 3, "seed_node_5": 3, "seed_node_6": 3, "seed_node_7": 3, "SENDER": 3, "Node_0": 3, "Node_1": 3, "Node_2": 3, "Node_3": 3, "Node_4": 3, "Node_5": 3, "Node_6": 3, "Node_7": 3}
Client {
base_nodes: {},
blocks: {},
miners: {},
ffi_wallets: {},
wallets: {},
merge_mining_proxies: {},
chat_clients: [],
transactions: {},
wallet_addresses: {},
utxos: {
"CB1": KeyManagerOutput {
version: V0,
value: MicroMinotari(
18462816327,
),
spending_key_id: Imported {
key: 7a3f9568ed491783667125a817e247beb26f0afe6af6cd641ae804521d8b0e47,
},
features: OutputFeatures {
version: V0,
output_type: Coinbase,
maturity: 3,
coinbase_extra: MaxSizeBytes {
inner: [],
},
sidechain_feature: None,
range_proof_type: BulletProofPlus,
},
script: TariScript {
script: MaxSizeVec {
vec: [
PushPubKey(
2a9fe859f232a17b1dcfd79039c2d563fed8153646056235303be32f438a677c,
),
],
_marker: PhantomData<tari_script::op_codes::Opcode>,
},
},
covenant: Covenant {
tokens: MaxSizeVec {
vec: [],
_marker: PhantomData<tari_core::covenants::token::CovenantToken>,
},
},
input_data: ExecutionStack {
items: [],
},
script_private_key_id: Imported {
key: 2a9fe859f232a17b1dcfd79039c2d563fed8153646056235303be32f438a677c,
},
sender_offset_public_key: ae549cd49bc467d35ba745897a3eac483c7e45ee6b28c0dc4f7dbbde7966c827,
metadata_signature: CommitmentAndPublicKeySignature {
ephemeral_commitment: HomomorphicCommitment(
54a7e4b9c0745c4efa85d6726e5f7ab75b48a0ac76d9dd5bca7fa03f13f4be58,
),
ephemeral_pubkey: 0c4cd2d45695fc911e1313bc0e798be042fda4409e5e6e4ea174613c844ec539,
u_a: RistrettoSecretKey(***),
u_x: RistrettoSecretKey(***),
u_y: RistrettoSecretKey(***),
},
script_lock_height: 0,
encrypted_data: EncryptedData {
data: MaxSizeBytes {
inner: [
71,
67,
70,
251,
69,
114,
241,
245,
83,
135,
68,
113,
59,
252,
133,
103,
64,
115,
155,
46,
194,
150,
11,
178,
193,
219,
12,
232,
254,
191,
239,
146,
238,
248,
197,
94,
181,
249,
169,
210,
192,
61,
44,
177,
240,
61,
225,
147,
77,
77,
165,
235,
127,
16,
39,
181,
48,
106,
228,
233,
109,
219,
50,
93,
230,
99,
26,
250,
55,
231,
195,
245,
174,
206,
159,
110,
38,
34,
234,
244,
],
},
},
minimum_value_promise: MicroMinotari(
0,
),
},
},
output_hash: None,
pre_image: None,
wallet_connected_to_base_node: {},
seed_nodes: [
"seed_node_0",
"seed_node_1",
"seed_node_2",
"seed_node_3",
"seed_node_4",
"seed_node_5",
"seed_node_6",
"seed_node_7",
],
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