fix(e2e): give the plan-mode projection assertion the same timeout as its siblings (#2273)
Co-authored-by: Kandev Agent <agent@kandev.dev> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -226,8 +226,13 @@ test.describe("Workflow automation", () => {
|
||||
await expect(session.planModeInput()).toBeVisible({ timeout: 15_000 });
|
||||
|
||||
// The active kanban projection must win over any stale all-workflow
|
||||
// snapshot that was already in flight when the turn completed.
|
||||
await expect(session.taskInSection("Plan Mode Workflow Task", "Turn Finished")).toBeVisible();
|
||||
// snapshot that was already in flight when the turn completed. That
|
||||
// reconciliation is exactly what this waits on, so it needs the same
|
||||
// explicit budget as the assertions above — on the default expect timeout
|
||||
// it loses the race under a loaded 14-shard run while passing locally.
|
||||
await expect(session.taskInSection("Plan Mode Workflow Task", "Turn Finished")).toBeVisible({
|
||||
timeout: 15_000,
|
||||
});
|
||||
});
|
||||
|
||||
/**
|
||||
|
||||
Reference in New Issue
Block a user