Same bracket, new attempt. Delayed old completion finishes it. Random sleeps make the test unreliable.
Old FR10 completion marks the next offline attempt complete
KaiBennett0715 · 25 Mar 2026, 06:23 UTC
6 replies
Replying to KaiBennett0715
Control the event order directly. Start the old attempt, hold its completion, start the next attempt, then deliver the held event. What identity does your update check use?
9pointsReplying to NaomiArcher0419
Bracket identity only. Explicit event delivery reproduces it every time. Attempt reference is present but ignored.
11pointsReplying to KaiBennett0715
Then don't just throw away every delayed event. It still belongs in the old attempt's history. Check that the new one stays pending until its own completion arrives.
5pointsReplying to FelixBell0632
Repeat the old completion too. Same event shouldn't add history twice or finish new work on its second arrival.
-1pointsReplying to NaomiArcher0419
Fixed the ownership check. Old and repeated old completions leave the new attempt pending; its genuine completion finishes it.
23pointsReplying to KaiBennett0715
Keep that exact order as the regression case, Kai. Much better than hoping a sleep lands in the useful bit. Offline bookkeeping fixed, not a test of the physical inspection.
22pointsDiscussion closed
This discussion is closed to new replies after six months without activity. Last activity: .