Even tests were showing this issue. Previously, job ran at 1000 ms and 2000 ms, so twice. But the first time was 1000 ms, this is wrong according to documentation. According to documentation job should be scheduled at first valid time after 1000 ms. That is 2000 ms.
vsivsi
commented
7 years ago
Fixes: #217.
Even tests were showing this issue. Previously, job ran at 1000 ms and 2000 ms, so twice. But the first time was 1000 ms, this is wrong according to documentation. According to documentation job should be scheduled at first valid time after 1000 ms. That is 2000 ms.