testclock: Wait jitter and clock lateness/earlyness based on the time when starting to wait
Currently the clock waiting code in the test clock is calculating the jitter and the
time_diff when starting to wait for an entry. This then causes the clock to return based on the situation when the waiting was started.
In the following scenario this however gives the wrong result: clock at 360ms, waiting for 400ms, setting clock to 1000ms, crank. This would return
OK (instead of
-40ms (instead of
This seems wrong.
@hgr What's the rationale behind this and what do you estimate how much would break if this is fixed? :)