A late result fools our job handler - fixture-check completion reporting

RachelAdams0174 · 9 Jul 2026, 20:43 UTC

Reply to discussion
RA
RachelAdams0174
I'm testing our fixture-check completion reporting tracking offline for a setup using Fairino FR5 in a sample inspection setup with recorded job events, with a fixture-mounted plate 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.

5 replies

AN
AnilBell0636
Replying to RachelAdams0174

Save the exact event order. Does your handler match the completion by attempt identity, or just the job label?

12 points
RA
RachelAdams0174
Replying to AnilBell0636

Our handler matches only the job label. The saved sequence reliably shows the earlier completion arriving after a new attempt begins and being attached to that new attempt.

7 points
AN
AnilBell0636
Replying to RachelAdams0174

Replay that sequence with explicit attempt matching. Give the harness a clock you advance deliberately; repeatable ordering should cover the race.

9 points
RA
RachelAdams0174
Replying to AnilBell0636

I've isolated the incorrect job-label match in a saved sequence. The remaining duplicate and delayed-event behaviour still needs establishing.

17 points
AN
AnilBell0636
Replying to RachelAdams0174

That's a clear partial result: an isolated identity mistake, with the other delivery cases still unverified.

13 points

Add to the discussion

Welcome to Application Robot

Everyone can read the forum. Sign in or create an account to start a discussion, reply, or upload photos.

Forgot your password?

By creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.