Repository navigation
Commit dae4374
test(e2e): poll restart task-history presence before asserting
What: runVerify now gates the Task should be present after restart
assertion on a bounded waitForTaskInHistory poll that uses the same
api.isTaskInHistory read as the assertion, instead of a single
unguarded read immediately after isReady.
Why: the e2e-mock lane failed on da8d752 with exactly this
assertion (false !== true) while the same commit passed 6/6 local
runs and the changed production paths cannot execute during the
scenario (watchdog tick 60s vs ~2s phases; the sidebar dispose
scoping is behavior-identical for the single watched view). The
read races the persisted state becoming observable on a fresh host,
the same swap-window failure class documented in Zoo-Code-Org#1641 for this
scenario, which Zoo-Code-Org#1663 fixed for the conversation-history reads but
left the isTaskInHistory read single-shot. Polling with the same
read removes the false negative without touching production code,
keeping the CodeRabbit-requested recovery and dispose guarantees
intact.1 parent 13f8ef0 commit dae4374
1 file changed
Lines changed: 9 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
35 | 35 | | |
36 | 36 | | |
37 | 37 | | |
| 38 | + | |
| 39 | + | |
| 40 | + | |
| 41 | + | |
| 42 | + | |
| 43 | + | |
| 44 | + | |
| 45 | + | |
38 | 46 | | |
39 | 47 | | |
40 | 48 | | |
| |||
99 | 107 | | |
100 | 108 | | |
101 | 109 | | |
| 110 | + | |
102 | 111 | | |
103 | 112 | | |
104 | 113 | | |
| |||
0 commit comments