CallumBarnes0534 · 26 Mar 2026, 15:37 UTC
Can the test queue the old completion explicitly, start the new attempt, and then deliver the queued event? That would let you assert the old attempt's state and that the new one is still waiting, without racing the clock.
8 pointsWe added an explicit event queue. The sequence fails every time now: start first attempt, retain its completion, start second, deliver the first completion. New attempt wrongly becomes complete.
18 pointsDoes that completion carry its own attempt identity, or does the handler have nothing more than the current job name to work with?
17 pointsKeep that reproducible failure in the handover even before the fix. Add a duplicated delivery and a genuine completion for the second attempt as separate cases; the person maintaining it needs to see what should remain unchanged and what should actually advance.
-3 pointsBy creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.