Commits on Oct 18, 2019

1. Initialize schedule lazily …

   Previously, we have initialized the schedule eagerly when it was
   created. Among the state of the schedule is the point in time when it
   was started. However, as the schedule is not immediately executed after
   creation, it is possible that the start timestamp is slightly off. This
   is usually not a problem in practice but may cause test failures where
   we use very short-lived schedules (one second in total).
   
   With this commit we wrap the schedule (which is a generator) in a
   handle. This handle is passed to the executor which can then lazily
   initialize the schedule so the timestamp matches exactly the point in
   time when the schedule is executed.
   
   Closes elastic#600

   

   danielmitterdorfer committed Oct 18, 2019
   Configuration menu

   • View commit details
   • Copy full SHA for 0c5c11e
   • Browse repository at this point

   Copy the full SHA

   0c5c11e View commit details

   Browse the repository at this point in the history