Repository navigation
chore(test): the mode_block session-API fixture times out on its first session create #1796
Description
Important
Problem — The session-API availability fixture in the mode-block tests failed once in main's CI right after the #1781 merge: its first session create hit the 60 s timeout. The re-run passed in 13 s; the same test took 8–13 s on every other recent CI run and passed 3 of 3 locally against the same engine. That first create also carries the engine's cold-start work (the plugin factory and a background package install into the test's empty home directory), and the failure output doesn't include the engine's log, so a slow install can't be told apart from a hung startup. An earlier flake in the same fixture (#829) was a teardown race, fixed in #831.
Approach — Print the engine's output on failure, and keep the cold-start install out of the timed step.
Acceptance Criteria
- When the first session create times out, the failure message includes the engine's output.
- The fixture passes 20 consecutive CI runs.
Notes
- Failing run:
mainCI on the fix(fleet): lossless, honest live event stream across the fleet (#1770) #1781 merge commit, first attempt; the second attempt was green. - Found during Fleet event stream is lossy by construction — remote sessions lag and desync during live activity #1770 post-merge (campaign advisory A18).
Activity