Stabilize recap bounded-concurrency timing test on main #689

Closed
opened 2026-08-12 23:33:27 +00:00 by timmy · 0 comments
Owner

Failure

The hourly release pulse fast-forwarded clean main to ad6c1edf80648215aab3db79bf8322d9101de279 and the required full suite failed consistently at tests/test_today_recap.py::test_recap_time_logging_attempts_multiple_entries_with_bounded_concurrency[asyncio].

Observed elapsed values were 0.357s and 0.361s against a hard <0.35s assertion. The focused test reproduced the failure. CI run 880 is green, so this appears host/timing-sensitive rather than a production behavior regression.

Acceptance

  • Preserve the assertion that five 100ms operations execute with bounded concurrency.
  • Replace the brittle wall-clock threshold with deterministic synchronization or a sufficiently robust behavioral assertion.
  • Focused test and full python3 -m pytest tests/ -q pass.
## Failure The hourly release pulse fast-forwarded clean `main` to `ad6c1edf80648215aab3db79bf8322d9101de279` and the required full suite failed consistently at `tests/test_today_recap.py::test_recap_time_logging_attempts_multiple_entries_with_bounded_concurrency[asyncio]`. Observed elapsed values were 0.357s and 0.361s against a hard `<0.35s` assertion. The focused test reproduced the failure. CI run 880 is green, so this appears host/timing-sensitive rather than a production behavior regression. ## Acceptance - Preserve the assertion that five 100ms operations execute with bounded concurrency. - Replace the brittle wall-clock threshold with deterministic synchronization or a sufficiently robust behavioral assertion. - Focused test and full `python3 -m pytest tests/ -q` pass.
timmy self-assigned this 2026-08-12 23:33:27 +00:00
timmy closed this issue 2026-08-12 23:55:25 +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#689
No description provided.