Repository navigation
test(desktop): fix flaky unassigned-project E2E #1923
Description
What happened
apps/desktop/e2e/project-management.spec.ts intermittently times out while waiting for the 未归属项目 group after creating and sending the first message in an unassigned session.
The assistant response is already visible when the test opens the sidebar and switches to project grouping, but no matching [data-project-id] appears within 10 seconds.
The same assertion has failed in unrelated CI runs:
- https://github.com/maka-agent/maka-agent/actions/runs/30754173380/job/91513384546
- https://github.com/maka-agent/maka-agent/actions/runs/30750871582/job/91504599212
- https://github.com/maka-agent/maka-agent/actions/runs/30754882624/job/91516939747
Adjacent CI runs pass, and the focused test passed 20/20 repeated runs on current main.
How to reproduce
- Run the full desktop E2E suite on the Ubuntu CI runner with one worker.
- Observe
project-management.spec.ts. - Intermittently, the final assertion cannot find the unassigned project group even though the fake backend response is visible.
The failure has not reproduced in 20 focused local runs.
Environment
- Maka commit:
5cb50df59 - CI: GitHub-hosted
ubuntu-latest - Node.js: 24
- Surface: Desktop Electron E2E
- Playwright workers: 1
- Retries: 0
Expected fix
Identify which state boundary has not settled before the final assertion and synchronize the test with that authoritative state. Do not hide the failure with retries or a longer timeout.
Verification should include repeated focused runs and the full desktop E2E suite.
Activity
Astro-Han commentedon Aug 2, 2026
I’m taking this. I’ll isolate whether the missing group comes from session-list convergence or the project-grouping transition, fix the actual synchronization boundary without retries, and verify the focused test under repetition plus the full desktop E2E suite.