Skip to content

test(replay): Fix flaky bufferStalledRequests segmentId assertion - #25394

Merged
mydea merged 1 commit into
developfrom
fix/replay-buffer-stalled-flaky
Oct 15, 2026
Merged

mydea merged 1 commit into
developfrom
fix/replay-buffer-stalled-flaky

Conversation

@mydea

@mydea mydea commented Oct 15, 2026

Copy link
Copy Markdown
Member

After the reload, the resumed session (now in session mode) flushes segment 1 after flushMinDelay (200ms), which bumps segmentId to 2. Snapshotting replay state could land on either side of that flush, so segmentId was sometimes 2.

Instead of snapshotting segmentId, the test now asserts that the first replay request sent after reload carries segment_id: 1 for the same replay, which verifies the same resumption behavior deterministically.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@mydea
mydea marked this pull request as ready for review October 15, 2026 12:32
@mydea
mydea requested a review from a team as a code owner October 15, 2026 12:33
@mydea
mydea requested review from logaretm and msonnb and removed request for a team October 15, 2026 12:33
@mydea
mydea merged commit 26c5cf2 into develop Oct 15, 2026
119 of 121 checks passed
@mydea
mydea deleted the fix/replay-buffer-stalled-flaky branch October 15, 2026 12:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants