简体中文界面。帖子、指南及政策正文保留原文;未对原文作自动翻译。

Old UR5e completion closes the newer attempt in our test

CallumBarnes0534 · 2026年3月26日 15:37 UTC

回复讨论
CA
CallumBarnes0534
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.

4 条回复

HA
HassanChan1052

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
CA
CallumBarnes0534

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
HA
HassanChan1052

Does that completion carry its own attempt identity, or does the handler have nothing more than the current job name to work with?

17
SO
SofiaBrooks0804

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

参与讨论

欢迎来到 Application Robot

所有人都可以阅读论坛。登录或注册后即可发起讨论、回复或上传照片。

忘记密码?

注册账号即表示你同意我们的 使用条款 社区准则。请阅读我们的 隐私政策 ,了解我们如何处理你的信息。