2adbd35a

By: Greg Pfeil <greg@technomadic.org>

qa: wait for wallet.py's balance to converge

`wallet.py` read the transparent balance shortly after mining and gave
it a five-block tolerance to catch up. The balance converges for several
seconds after the wallet reaches the chain tip, and while converging it
can be most of the chain behind, so the tolerance was much smaller than
the real lag: locally 55 and 66 coinbases where 96 to 101 were expected,
and 43 in CI.

No `getwalletstatus` field says when the balance view is complete, so
poll for the expected amount, as the other convergence helpers here
already do. That is a timing bound rather than a guarantee -- observed
convergence is around 3s against a 60s budget -- but it asserts the
exact amount, and on timeout fails with the balance it actually saw
instead of accepting a partial one.

Verified against the zaino backend: five consecutive passes, where the
previous version failed twice in two.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Total

5s

Timeline