test(sync): allow serialized bounded negentropy rounds

The connection-wide request ledger and paced descendant rotation may serialize historic negentropy rounds. The integration scenario still required overlap, even though overlap is not a correctness guarantee and the newer scheduling model deliberately permits a peak of one.

Keep the safety and workload assertions: all sampled events must arrive, the proxy must reject zero rounds, peak concurrency must stay within the production bound, and total rounds must exceed that bound. Unit coverage continues to exercise concurrent ledger admission directly.

Validated by the focused scenario through every assertion except the removed overlap-only lower bound.
This commit is contained in:
DanConwayDev
2026-08-12 15:37:26 +00:00
parent 9b49056a14
commit d324a320a8
-5
View File
@@ -213,11 +213,6 @@ async fn startup_historic_sync_stays_within_relay_neg_concurrency_limit() {
"peak concurrent NEG rounds {} exceeded the bound {PROXY_NEG_LIMIT}",
proxy.peak_concurrent()
);
assert!(
proxy.peak_concurrent() >= 2,
"negentropy rounds should still overlap under the bound, peak: {}",
proxy.peak_concurrent()
);
assert!(
opened > PROXY_NEG_LIMIT,
"scenario must run more rounds than the bound to exercise queueing, opened: {opened}"