Our retry bookkeeping needs a tougher offline test (sample acceptance bookkeeping)

CalebAdams0145 · 2026年9月2日 14:31 UTC

回复讨论

主帖中文翻译暂不可用,以下显示英文原文;回复保留原文。 查看英文原文

CA
CalebAdams0145
I'm testing our sample acceptance bookkeeping tracking offline for a setup using Universal Robots UR5e in a workshop fixture-checking station, with a sample bracket as a reference. An earlier attempt's completion incorrectly completes a newer attempt if I deliver it after that attempt starts. I need repeatable delayed and duplicate event tests because the random sleeps aren't reliable.

10 条回复

HE
HenryAdams0090

@CalebAdams0145 Can you preserve that failing delivery sequence and check which identifier the handler uses to match completion: the specific attempt or only the job label?

10分
CA
CalebAdams0145

Just the job label. I've saved the sequence: earlier completion arrives after the new attempt starts. It reproduces the wrong match.

23分
HE
HenryAdams0090

Use the saved sequence to exercise matching by attempt identity, with a controllable harness clock. Making the ordering deterministic should cover this race condition.

16分
CA
CallumChen1143

@HenryAdams0090 It covers that order, not every race. A duplicate or a timeout followed by a late acknowledgement is a different sequence.

5分
HE
HenryAdams0090

You're right; my coverage claim was too broad. This schedule targets the reproduced mismatch, and the duplicate and post-timeout acknowledgement cases need their own schedules.

21分
CA
CalebAdams0145

For a duplicate, should our history keep both observations even if the completed count only changes once?

19分
HE
HenryAdams0090

@CalebAdams0145 Keep the duplicate in diagnostic history while making the completion update idempotent, so receiving it again doesn't alter the accepted result or count.

4分
RE
RebeccaBaker0517

Is idempotent just another word for ignoring the second message? I'm not sure how that fits with retaining it in the history.

6分
HE
HenryAdams0090

Idempotence means reapplying the message doesn't change the result again. Recording that it arrived is separate from repeating the completion or count update.

18分
YA
YasminBarnes0528

My offline test used to assert only the final count. It missed a duplicate notification because the number happened to stay right.

12分

参与讨论

欢迎来到 Application Robot

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

忘记密码?

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