Skip to content

ci(smoke): keep containers on failed runs; dump user state on reply timeout - #570

Merged
futurepaul merged 2 commits into
mainfrom
ci/smoke-observability
Aug 18, 2026
Merged

ci(smoke): keep containers on failed runs; dump user state on reply timeout#570
futurepaul merged 2 commits into
mainfrom
ci/smoke-observability

Conversation

@futurepaul

Copy link
Copy Markdown
Contributor

Two observability gaps found during the 2026-08-18 depot smoke hunt:

  • --keep-running only applied on the success path — a failed run deleted exactly the container you need to inspect. Now honored on failure too.
  • A reply-timeout carried only the last 8 messages. The failure now includes a bounded user-runtime state summary (rooms, unread counts, topics, selected ids), which distinguishes 'reply never arrived' from 'room wedged' from 'reply routed to another topic'.

No behavior change to the passing path. Durable-home suite green locally.

…ounded user state on reply timeout

Two observability gaps from the 2026-08-18 depot smoke hunt: --keep-running
only applied on the success path (a failed run removed exactly the container
you need to inspect), and a reply-timeout carried only the last 8 messages —
no user-runtime room/topic/unread state, leaving 'user side never observed
the reply' indistinguishable from 'reply never sent'.
The converging-stub cases need three poll rounds at a 1s poll interval;
a 2s wall-clock budget raced the poll cadence and failed under CI load
(PR #570 run 32173170068, Brain acceptance matrix). The convergence
check runs before the deadline check each round, so the budget only
needs to comfortably cover the round count. Failure-path budgets stay
at 1s; those stubs never converge and are deterministic.
@futurepaul
futurepaul merged commit 510e68b into main Aug 18, 2026
26 of 28 checks passed
@futurepaul
futurepaul deleted the ci/smoke-observability branch August 18, 2026 21:57
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.

1 participant