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 · 2026年3月26日 15:37 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
4 条回复
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分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.
18分Does that completion carry its own attempt identity, or does the handler have nothing more than the current job name to work with?
17分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.
-3分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .