Our offline handler accepts an old completion against whichever fixture-check attempt is current. Random sleeps reproduce it only sometimes. I want to choose the event order deliberately and check both attempts afterwards.
Old UR5e completion closes the newer attempt in our test
CallumBarnes0534 · 26 Mar 2026, 15:37 UTC
4 replies
Replying to CallumBarnes0534
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.
8pointsReplying to HassanChan1052
We 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.
18pointsReplying to CallumBarnes0534
Does that completion carry its own attempt identity, or does the handler have nothing more than the current job name to work with?
17pointsReplying to CallumBarnes0534
Keep 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.
-3pointsDiscussion closed
This discussion is closed to new replies after six months without activity. Last activity: .