main is red: CI failure at f5f4f2d #862

Activity

1. github-actions

   assigned

   taras

   on Sep 30, 2026
2. github-actions

   added

   ci-main-redCI concluded red on main; closes itself when main recoversCI concluded red on main; closes itself when main recovers

   on Sep 30, 2026
3. taras commented on Sep 30, 2026

   

   taras

   on Sep 30, 2026

   Owner

   More actions

   Diagnosed and repaired in #863.

   Cause. The Slice D U1 conversation-order row in packages/cli/tests/repl-agent-interface.test.ts waits for the two turns that report a provider conversation (started(session) === 2), then expects clearing the filter to restore three turn rows. The third scripted <Spawn> is queued, so it never reports a conversation and never contributes to that wait — but its row exists as soon as its Prompt is observed. The assertion therefore depended on which spawn the scheduler reached first. Run 36786555733 read two slots (build · streaming, review · completed, recorded) where the row expected three.

   Blast radius. One test row. No product job failed, and the same corpus passed under Node and Bun. green failed only because test-deno is in its needs.

   Repair. One readiness wait — until(session, "all three Prompts being observed", () => observed(session) === 3) — added after the existing conversation wait, which stays because the ordering assertions need it. No production change. Every other three-row assertion in the file is already gated by observed(session) === 3 or by all three coroutines finishing.

   Leaving this issue open: it closes itself when CI next succeeds on main.
4. github-actions commented on Sep 30, 2026

   

   github-actionsBot

   on Sep 30, 2026 – with GitHub Actions

   Author

   More actions

   ✅ main is green again at 4af3009 — run.
5. github-actions

   closed this as completedon Sep 30, 2026