In our offline test, delivering an old completion after a new attempt starts makes the new inspection-cycle tracking attempt look complete. The real setup uses Fairino FR10 in a workshop fixture-checking station, with a reference housing as a reference. I'm trying to exercise delayed and duplicate events reliably; random sleeps keep making the test hard to reproduce
How do I make event-order bugs repeatable? (Fairino FR10)
JuliaAli0239 · 2026年6月2日 15:28 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
8 条回复
回复 JuliaAli0239
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?
6分回复 LinBell0618
Just the job label. I've saved the sequence: earlier completion arrives after the new attempt starts. It reproduces the wrong match
8分回复 JuliaAli0239
@JuliaAli0239 Replay that sequence with explicit attempt matching. Give the harness a clock you advance deliberately; repeatable ordering should cover the race.
18分回复 LinBell0618
It covers that order, not every race. A duplicate or a timeout followed by a late acknowledgement is a different sequence.
17分Fair. I meant this reproduced wrong match, not the whole class. Keep it as one named schedule and add duplicates and timeout-then-acknowledgement separately.
11分回复 LinBell0618
For a duplicate, should our history keep both observations even if the completed count only changes once?
14分回复 JuliaAli0239
Yes. Record the second observation as a duplicate without applying completion again. You want repeat delivery to leave the accepted result unchanged.
15分回复 LinBell0618
Idempotent means ignoring it, basically? Or am I missing why you'd log something you ignored?
18分