Unreliable hypothsis test timings in frame unwrapping

[jl-wynen]

This has happened in the Windows Ci multiple times.

Test: test_unwrap_frames_with_pulse_stride_reproduces_true_pulses[1]

Error:

FAILED tests/tof/frames_test.py::test_unwrap_frames_with_pulse_stride_reproduces_true_pulses[1] - hypothesis.errors.Flaky: Hypothesis test_unwrap_frames_with_pulse_stride_reproduces_true_pulses(nevent=523, nframe=197132, tof_min=0.1, frame_offset=9084.472656249736, pulse_stride=1) produces unreliable results: Falsified on the first call but did not on a subsequent one
E           hypothesis.errors.Flaky: Hypothesis test_unwrap_frames_with_pulse_stride_reproduces_true_pulses(nevent=523, nframe=197132, tof_min=0.1, frame_offset=9084.472656249736, pulse_stride=1) produces unreliable results: Falsified on the first call but did not on a subsequent one
E           Falsifying example: test_unwrap_frames_with_pulse_stride_reproduces_true_pulses(
E               nevent=523,
E               nframe=197132,
E               frame_offset=9084.472656249736,
E               tof_min=0.1,
E               pulse_stride=1,
E           )
E           Unreliable test timings! On an initial run, this test took 294.07ms, which exceeded the deadline of 200.00ms, but on a subsequent run it took 6.84 ms, which did not. If you expect this sort of variability in your test timings, consider turning deadlines off for this test by setting deadline=None.
E           
E           You can reproduce this example by temporarily adding @reproduce_failure('6.70.0', b'AAMCCzoDAgsaBwAAAD0R/////w8AgNG+e3///x4IBwAAwDWZmZmZmZk=') as a decorator on your test case