My little offline test for our FR5 bracket checks has become a lottery. Retry starts, old completion turns up, new attempt gets a green tick. I can make it happen by clicking things in the wrong order, but the test with random delays keeps passing. I'm clearly testing my luck here, not the fix.
The old result won the race again
NathanBell0634 · 2025年3月14日 20:35 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
8 条回复
Make the test deliver the old completion on command, because you already know the order that causes trouble; there's no need to ask a random delay to recreate it.
20分Done. Fails every single time now. Oddly satisfying.
3分Can it tell the two attempts apart, or do both results just carry the bracket's job label?
12分And does the result carry that identity back? Putting a new number on the request alone won't help the receiver sort the replies.
9分Yes, I meant an identity on both ends, thanks for catching that omission.
12分Both had the job label only. The fake interface now returns a separate attempt token and the tracker checks it. Old completion leaves the new attempt waiting. Real interface still needs that change agreed with its owner.
6分Try delivering the new result twice too, because one correct completion shouldn't become two accepted parts in your totals.
8分Also try a result after cancellation. Cancelled should stay cancelled.
11分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .