test: feature_asset_locks intermittent llmq_test_platform quorum timeout

[thepastaclaw]

Summary

feature_asset_locks.py intermittently times out while waiting for a freshly mined llmq_test_platform quorum to appear in quorum list.

This reappeared in PR #7309, but that PR only changes Qt file dialog code (src/qt/bitcoin.cpp, src/qt/guiutil.cpp, src/qt/guiutil.h, src/qt/intro.cpp). The failing test is unrelated to the PR diff. The latest develop CI for the PR base (5fd84aa23de0d79770bfc25c4c1393eb4eadbcf8) is green, so this looks intermittent rather than a deterministic base failure.

A previous closed issue, #6748, captured the same failure mode in feature_asset_locks.py at the same wait_for_quorum_list() point.

CI evidence

PR: #7309 (fix(qt): add non-native file dialog option)

Failing check:

• linux64-test / Test source
• run/job: https://github.com/dashpay/dash/actions/runs/25496950766/job/74825897605

Failure:

TestFramework (INFO): Mining next quorum to check tx 'asset_unlock_tx_late' is still valid...
TestFramework (INFO): Mining quorum: llmq_type_name=llmq_test_platform, llmq_type=106, expected_members=2, expected_connections=1, expected_contributions=2, expected_commitments=2
TestFramework (INFO): Waiting for quorum to appear in the list
...
AssertionError: Predicate ''''
        def wait_func():
            return quorum_hash in self.nodes[0].quorum('list')[llmq_type_name]
''' not true after 60.0 seconds

Stack:

feature_asset_locks.py:430 test_asset_unlocks()
feature_asset_locks.py:246 mine_quorum_2_nodes()
test_framework.py:2208 mine_quorum()
test_framework.py:2123 wait_for_quorum_list()

Scope check

PR #7309 touches only Qt GUI file dialog plumbing:

src/qt/bitcoin.cpp
src/qt/guiutil.cpp
src/qt/guiutil.h
src/qt/intro.cpp

No functional test, quorum, consensus, mempool, asset lock, or LLMQ code is changed by the PR.

Prior matching failure

Closed issue #6748 reported the same feature_asset_locks.py flake with the same wait_for_quorum_list() predicate timeout while mining an llmq_test_platform quorum for asset_unlock_tx_late.

Conclusion

This appears to be a pre-existing intermittent feature_asset_locks.py / LLMQ test timing flake, not a regression caused by #7309.

[thepastaclaw]

Additional CI evidence from #7329:

• PR: test: stabilize governance superblock waits #7329 (test: stabilize governance superblock waits)
• Failing check: linux64_sqlite-test / Test source
• run/job: https://github.com/dashpay/dash/actions/runs/26021664791/job/76491427766

Scope check: #7329 only changes:

test/functional/feature_governance.py
test/functional/test_framework/governance.py

It does not touch feature_asset_locks.py, LLMQ, asset locks, mempool sync, or consensus code.

Observed failure mode in feature_asset_locks.py after two earlier failed attempts and a final long-running attempt:

feature_asset_locks.py:452 in test_asset_unlocks
  self.generate_batch(25)
feature_asset_locks.py:240 in generate_batch
  self.generate(self.nodes[1], batch)
test_framework.py:878 in sync_all
  self.sync_mempools(nodes)
test_framework.py:871 in sync_mempools
  raise AssertionError("Mempool sync timed out after {}s:{}".format(...))

AssertionError: Mempool sync timed out after 240s:
  {'580775b273851cb8a7704f1fb2111677eaa49133e2f0c872821baaa382179aa8',
   '8a92e18cf1dc7339ef1c48c6550402463804faf202c27c8e0f2cb772a3cfea28',
   'a2487ae374e2b1c870c091af481178f606e13b1c9dc781091b88fb2d5315496f'}
  set()
  set()
  set()

The failed run was on PR head fefdd42fc87ec7cc51b4cf97349390a8dc1b3b96. This looks like another pre-existing intermittent feature_asset_locks.py timing/sync failure, not caused by #7329.