Offline FR5 tracker accepts an old result after retry starts. Random delays rarely catch it. Any straightforward test?
An old housing result finishes the new check
JonasChan1068 · 2025年4月20日 08:23 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
4 条回复
Hold the old result in a fake event source, start the retry, then deliver it yourself. You want that exact ordering every run, not another timing raffle.
7分That reproduces it. Both attempts use the same housing label, no separate attempt identity.
17分Have you agreed an attempt identifier that comes back with the result? The test can check matching, but the real interface must supply the information too.
19分Also deliver the right result twice. Count the housing once. Easy bug to leave beside the one you've just found.
-4分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .