From 3a4a591f7d91b4f89f5b798c9d4812fb7042a527 Mon Sep 17 00:00:00 2001 From: pasta Date: Mon, 16 Nov 2026 04:56:47 +0000 Subject: [PATCH] test: wait for a ChainLock only on a block the healed quorum signs feature_llmq_data_recovery.py heals one quorum and then expects the next block to be chainlocked. Two llmq_test quorums are active, and the ChainLock for a height can fall to either. The other quorum lost its key shares to the same reindex, and the test never waits for it to recover. When it is picked, its members either have no key share yet or the recovery member chosen for the session has no verification vector and drops every share, and nothing re-signs the tip, so the wait times out. Mine until selectquorum names the healed quorum for the tip, then wait for its ChainLock. Co-Authored-By: Claude Opus 5.5 --- test/functional/feature_llmq_data_recovery.py | 19 ++++++++++++++----- 1 file changed, 14 insertions(+), 5 deletions(-) diff --git a/test/functional/feature_llmq_data_recovery.py b/test/functional/feature_llmq_data_recovery.py index 539354eebfbd..62f8f0150b35 100755 --- a/test/functional/feature_llmq_data_recovery.py +++ b/test/functional/feature_llmq_data_recovery.py @@ -30,6 +30,10 @@ RECOVERY_TRIGGER_LOG = "TriggerQuorumDataRecoveryThreads -- Process block" +def clsig_request_id(height): + return hash256(ser_string(b"clsig") + struct.pack("