Commit 12cc3cb
committed
Fix flaky dst_notify_timeout_recovers_from_lag test
The test assumed flooding 200 events through DstEventSource would cause
the broadcast channel to lag. In practice, the worker and task interleave
event processing so the receiver drains events as fast as they arrive,
preventing lag. After the flood, the task was stuck in the select loop
with no matching event and no lag error.
Fix by also sending the real notification event after the flood. The task
now completes regardless of whether lag occurs: either through the Lagged
recovery path (re-poll DB) or through the normal broadcast path.
https://claude.ai/code/session_01CxLxPCCymXVh9ob6wL5X161 parent 3423a32 commit 12cc3cb
1 file changed
+12
-4
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
353 | 353 | | |
354 | 354 | | |
355 | 355 | | |
356 | | - | |
357 | | - | |
358 | | - | |
| 356 | + | |
| 357 | + | |
| 358 | + | |
| 359 | + | |
| 360 | + | |
| 361 | + | |
| 362 | + | |
| 363 | + | |
| 364 | + | |
| 365 | + | |
| 366 | + | |
359 | 367 | | |
360 | 368 | | |
361 | 369 | | |
362 | | - | |
| 370 | + | |
363 | 371 | | |
364 | 372 | | |
365 | 373 | | |
| |||
0 commit comments