The main (test) thread is kept in a blocking wait until the planned schedule is completed. If however the schedule overruns, the wake-up job could just be triggered prematurely. This can easily be prevented by adding a dependency from the last computation job to the wake-up job. If the computation somehow flounders, the SAFETY_TIMEOUT (5s) will eventually raise an exception to let the test fail cleanly (shutting down the Scheduler automatically) |
||
|---|---|---|
| .. | ||
| gear | ||
| mem | ||
| DIR_INFO | ||