[CI-GLOBAL] dashpay/dash — linux64_tsan-test flaky interface_zmq_dash timeout

[thepastaclaw]

Affected PRs

• test: add deserialization fuzz targets for Dash-specific types dashpay/dash#7161
• build: default --enable-stacktraces to auto for graceful fallback dashpay/dash#7163
• test: use BOOST_REQUIRE for fatal preconditions in coinjoin_tests dashpay/dash#7164

Failing check

linux64_tsan-test / Test source — fails on all 3 PRs above (build passes, test fails)

Run URLs

• #7161 run
• #7163 run
• #7164 run

Fingerprint

AssertionError: Predicate not true after N seconds
interface_zmq_dash test
Unable to bind to 127.0.0.1:19896 on this computer. Dash Core is probably already running.

Test interface_zmq_dash times out under ThreadSanitizer. Port binding failure suggests resource contention on CI runners.

Classification

Systemic/global. Same linux64_tsan-test failure on 3 different dash PRs with unrelated code changes. Appears to be a flaky test or CI runner resource issue, not caused by any PR's code.

Severity

Non-blocking — TSan test is informational for these PRs. Other CI checks (build, other tests) pass.

[thepastaclaw]

Update 2026-02-22 17:01 CT

Flaky test failures continue to spread across dash PRs:

Newly affected:

• dash#7165: linux64_sqlite-test — same AssertionError: Predicate not true after N seconds + port binding failure pattern
• dash#7167: linux64-test — AssertionError: not(3 == 2) — different assertion but same flaky test infrastructure

Still affected from before:

• dash#7161, #7163, #7164: linux64_tsan-test

Total: 5 of 8 open dash PRs have flaky test failures. The failures span multiple test configurations (tsan, sqlite, regular linux64) suggesting a systemic CI runner issue rather than a specific test config problem.

Other dash#7167 note: Also has Validate PR title failure despite title looking valid (test(fuzz): add BLS operations and IES encryption fuzz targets). May be transient.

[thepastaclaw]

Update 2026-02-22 17:31 CT

Additional spread of the same dash CI flakiness:

• dash#7168 now also failing linux64_sqlite-test / Test source (in addition to Validate PR title)
• This matches the same failure class already seen on dash#7165 (sqlite), plus tsan/linux64 failures on other PRs.

Current affected dash PRs with flaky test failures:

• #7161 (linux64_tsan-test)
• #7163 (linux64_tsan-test)
• #7164 (linux64_tsan-test)
• #7165 (linux64_sqlite-test)
• #7167 (linux64-test)
• #7168 (linux64_sqlite-test)

So this is now 6/8 open dash PRs impacted by CI test flakiness across multiple test variants (tsan/sqlite/linux64).

[thepastaclaw]

Update 2026-02-22 23:01 CT

Newly affected dash PR:

• dash#7171 now fails linux64_multiprocess-test / Test source
  • run: https://github.com/dashpay/dash/actions/runs/22291981703/job/64483022591

Fingerprint matches existing flaky CI pattern:

• AssertionError: Predicate not true after ...
• Unable to bind to 127.0.0.1:19896 ... Dash Core is probably already running

This is consistent with the existing systemic test-environment contention tracked here (not PR-local logic failure).