From 1a2c3a8cfba8bd041e0dde7a984afbd341f9b23d Mon Sep 17 00:00:00 2001 From: DanConwayDev Date: Mon, 17 Aug 2026 11:59:49 +0000 Subject: [PATCH] test(sync): expose rejection ordering barriers Two maintainer-reprocessing tests wait on per-event rejection diagnostics, but the logging severity merge demoted those records to debug while their relay fixtures retained the info default. The bounded waits therefore failed deterministically even though reprocessing remained healthy. Start only the two affected fixtures through the existing debug-enabled helper. This preserves production-like logging for unrelated tests and keeps the observable ordering barriers introduced to replace fixed sleeps. This assumes the rejection diagnostic remains available at debug. Production behavior, global test logging, cache configuration, and the stacked storage PR lint failures are deliberately excluded. Validated with both focused integration tests under the normal environment, cargo fmt --all -- --check, and git diff --check. --- tests/sync/maintainer_reprocessing.rs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tests/sync/maintainer_reprocessing.rs b/tests/sync/maintainer_reprocessing.rs index 9f37e24..1f14277 100644 --- a/tests/sync/maintainer_reprocessing.rs +++ b/tests/sync/maintainer_reprocessing.rs @@ -1400,7 +1400,7 @@ async fn test_maintainer_announcement_reprocessed_immediately() { // Step 2: Start relay_b with relay_a as bootstrap so its SyncManager connects immediately. // relay_b's initial negentropy sync will pick up the maintainer announcement and reject it // (no owner announcement in relay_b's DB yet), storing it in the hot cache. - let relay_b = TestRelay::start_with_sync(Some(relay_a.url().to_string())).await; + let relay_b = TestRelay::start_with_sync_debug(Some(relay_a.url().to_string())).await; println!("relay_b started at {}", relay_b.url()); // Wait for relay_b's initial negentropy sync on its observable outcome: @@ -1607,7 +1607,7 @@ async fn test_multiple_maintainers_all_reprocessed() { // Because all three maintainer announcements are confirmed in relay_a's DB, relay_b's // initial negentropy sync will pick them all up and reject them (no owner announcement // in relay_b's DB yet), storing them in the hot cache. - let relay_b = TestRelay::start_with_sync(Some(relay_a.url().to_string())).await; + let relay_b = TestRelay::start_with_sync_debug(Some(relay_a.url().to_string())).await; println!("relay_b started at {}", relay_b.url()); // Wait for relay_b's initial negentropy sync on its observable outcome: