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 · 20 Apr 2025, 08:23 UTC
4 replies
Replying to JonasChan1068
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.
7pointsReplying to MinaBrooks0859
That reproduces it. Both attempts use the same housing label, no separate attempt identity.
17pointsReplying to JonasChan1068
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.
19pointsReplying to JonasChan1068
Also deliver the right result twice. Count the housing once. Easy bug to leave beside the one you've just found.
-4pointsDiscussion closed
This discussion is closed to new replies after six months without activity. Last activity: .