Fix flaky live-snapshot freshness test blocking CI release #819

Closed
opened 2026-08-14 10:10:48 +00:00 by timmy · 0 comments
Owner

Failure evidence

Gitea Actions run 1026 (push to main at commit 0c71dea00c47) failed in tests/test_live_snapshot.py::test_live_snapshot_reuses_completed_snapshot_inside_freshness_window[asyncio]: expected user_calls == 1, observed 0. The same checkout passed locally, indicating a scheduler-sensitive race in the test or snapshot coordination. Build and release-candidate jobs were blocked.

Acceptance criteria

  • The test deterministically observes the first snapshot computation before asserting coalescing behavior.
  • The focused test passes repeatedly without timing-dependent polling.
  • Full python3 -m pytest tests/ -q passes.
  • A Closes #N PR contains test evidence and restores green CI/release flow.
## Failure evidence Gitea Actions run 1026 (push to `main` at commit `0c71dea00c47`) failed in `tests/test_live_snapshot.py::test_live_snapshot_reuses_completed_snapshot_inside_freshness_window[asyncio]`: expected `user_calls == 1`, observed `0`. The same checkout passed locally, indicating a scheduler-sensitive race in the test or snapshot coordination. Build and release-candidate jobs were blocked. ## Acceptance criteria - [ ] The test deterministically observes the first snapshot computation before asserting coalescing behavior. - [ ] The focused test passes repeatedly without timing-dependent polling. - [ ] Full `python3 -m pytest tests/ -q` passes. - [ ] A `Closes #N` PR contains test evidence and restores green CI/release flow.
timmy self-assigned this 2026-08-14 10:10:48 +00:00
timmy closed this issue 2026-08-14 10:24:47 +00:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: stackchain/stackchain-dashboard#819
No description provided.