From febb85a7b4bb14a286555eab6e34a217d74af9a1 Mon Sep 17 00:00:00 2001 From: zzstoatzz Date: Fri, 24 Jul 2026 16:22:58 -0500 Subject: [PATCH] tests: correct stale archive-contract sealed-frontier expectations archive-contract has also been failing on main and was outside the last chunk's rerun set. Its --backfill-only replays expected 5,000 events, the whole sample archive. The sample's third segment is active and unsealed and startup now resumes it in place, so the segment-download API correctly serves the sealed frontier at seq 4000. Expectations move to the sealed frontier and the comment states why. The full archive-to-live cutover in the same file is deliberately left at 5,000 and still passes, so the suite now pins both sides of that boundary rather than conflating them. Whole suite green against pinned upstream client f29815c. Co-Authored-By: Claude Opus 5 (1M context) --- tests/archive_client_e2e.py | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-) diff --git a/tests/archive_client_e2e.py b/tests/archive_client_e2e.py index 80029d6..84b0454 100644 --- a/tests/archive_client_e2e.py +++ b/tests/archive_client_e2e.py @@ -103,20 +103,25 @@ def replay(name, expected_count, expected_first, expected_last, *filters): print(f"{name}: PASS ({len(rows)} rows, {cursors[0]}..{cursors[-1]})") -replay("whole-segment", 5000, 1, 5000) +# --backfill-only reaches the SEALED frontier, not the archive tip. The sample +# leaves its third segment active (unsealed) and startup resumes it in place as +# upstream's ingest.Open does, so these stop at seq 4000. The full cutover run +# below has no such bound and must still reach all 5,000 events -- that gap is +# the boundary, not a shortfall. +replay("whole-segment", 4000, 1, 4000) replay( "did-block-plan", - 2500, + 2000, 2, - 5000, + 4000, "--did", "did:plc:streamsampleaccount", ) replay( "sentinel-only-block-plan", - 50, + 40, 100, - 5000, + 4000, "--collection", "com.example.nothing", ) -- 2.51.2