Our offline UR5e bracket tracker assigns an earlier attempt's completion to the current attempt if it arrives late, but the random-delay test does not reliably create that order; what should I ask the developer to control explicitly?
Cannot reproduce our UR5e bracket result mix-up with random delays
NaomiBennett0767 · 2025年12月30日 09:45 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
1 条回复
Control the event order and test clock. Specify both attempt identities, start them deliberately, then deliver the old result while the new attempt is pending and again after it finishes. Assert both attempt states and the physical bracket count after each step. Add duplicate delivery, unknown identity and restart cases separately. None should need a random sleep or a new physical inspection request.
9分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .