feature_llmq_signing.py --spork21 flaky on v23.1.x
Summary
feature_llmq_signing.py --spork21 is still intermittently failing on the
v23.1.x CI lane with the known wait_for_sigs(True, False, True, 15)
timeout. This appears to be the same failure tracked previously in
#7255 and fixed on develop by #7289, but #7289 is not present on
v23.1.x.
Latest occurrence
Traceback excerpt:
File "test/functional/feature_llmq_signing.py", line 111, in run_test
wait_for_sigs(True, False, True, 15)
File "test/functional/feature_llmq_signing.py", line 60, in wait_for_sigs
self.wait_until(lambda: check_sigs(...), timeout = timeout)
AssertionError: Predicate ... not true after 60.0 seconds
Scope check
The triggering PR only changes:
.github/workflows/predict-conflicts.yml
It does not touch source code, test-src.yml, feature_llmq_signing.py, or
the functional test framework. The failure is therefore not caused by #7322.
Existing diagnosis
Issue #7255 tracked this exact intermittent feature_llmq_signing.py --spork21
timeout and was closed as fixed by #7289. That fix merged to develop as:
upstream/v23.1.x does not contain 8c42e829b3 / #7289, so the release
branch can still hit the old flake.
Suggested resolution
Backport #7289 to v23.1.x if the fix is appropriate for the release branch,
or otherwise mark/handle this test as known flaky on v23.1.x CI.
feature_llmq_signing.py --spork21flaky onv23.1.xSummary
feature_llmq_signing.py --spork21is still intermittently failing on thev23.1.xCI lane with the knownwait_for_sigs(True, False, True, 15)timeout. This appears to be the same failure tracked previously in
#7255 and fixed on
developby #7289, but #7289 is not present onv23.1.x.Latest occurrence
ci: tolerate conflict comment permission errors)6948ad3c273d2f1a4848877bf985347de08c1379v23.1.xhttps://github.com/dashpay/dash/actions/runs/25917464462/job/76187839723
linux64_multiprocess-test / Test sourcefeature_llmq_signing.py --spork21Traceback excerpt:
Scope check
The triggering PR only changes:
It does not touch source code,
test-src.yml,feature_llmq_signing.py, orthe functional test framework. The failure is therefore not caused by #7322.
Existing diagnosis
Issue #7255 tracked this exact intermittent
feature_llmq_signing.py --spork21timeout and was closed as fixed by #7289. That fix merged to
developas:8c42e829b3— Merge revert: "fix: avoid improper dual way connection attempts" + tests #72890e33aa2a9d— revert: "fix: avoid improper dual way connection attempts"c1cdb751e4— test: assert QSENDRECSIGS handshake is symmetric under spork21upstream/v23.1.xdoes not contain8c42e829b3/ #7289, so the releasebranch can still hit the old flake.
Suggested resolution
Backport #7289 to
v23.1.xif the fix is appropriate for the release branch,or otherwise mark/handle this test as known flaky on
v23.1.xCI.