8000 test(e2e): keep S-023's busy run in the conversation by geminixiang · Pull Request #202 · geminixiang/mikan · GitHub
[go: up one dir, main page]

Skip to content

test(e2e): keep S-023's busy run in the conversation - #202

Merged
geminixiang merged 1 commit into
mainfrom
test/e2e-busy-queue-in-conversation
Oct 26, 2026
Merged

geminixiang merged 1 commit into
mainfrom
test/e2e-busy-queue-in-conversation

Conversation

@geminixiang
Copy link
Copy Markdown
Owner

S-023 checks that a message sent while mikan is busy is queued and answered. Since #193 offers start_task in channels, the model may admit the busy request as a background task. The task's reply then goes to the task thread, which S-023 does not poll, and the channel is never busy, so the case stops testing queueing.

Evidence from four Slack E2E runs on 2026-10-26 (the simplification PRs #197, #198, #200, #201):

Run branch start_task used S-023
refactor/simplify-sessions yes fail: no reply in the busy thread; the task thread got the token at +17s
refactor/simplify-adapters no pass
refactor/simplify-harness no pass
refactor/simplify-sandbox-settings yes fail, same way

The daemon log shows intake, the task admission, and the token reply for both failures, so delivery was correct.

Change: the busy prompt asks the model to run sleep 10 in this conversation, not as a background task. Test-only, so done when CI and a Slack E2E run on this branch pass.

Since channels offer start_task (#193), the model may hand the busy run to a
background task. Its reply then lands in the task thread, outside the thread
S-023 polls, and the channel is never busy, so the case no longer tests
queueing. Two of four runs on 2026-10-26 failed this way; both used start_task.
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

0