https://bugs.kde.org/show_bug.cgi?id=397776
Bug ID: 397776
Summary: Aborted job with given startup time not restarted
Product: kstars
Version: 2.9.8
Platform: unspecified
OS: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: mutla...@ikarustech.com
Reporter: wreis...@gmx.de
Target Milestone: ---
A SchedulerJob with a given startup-time, that aborts for example because
guiding temporarily fails, will be set to "invalid" as soon as the scheduler
tries to restart it.
It seems like there is a misinterpretation what "start at" means. Currently, it
defines a short timeframe of startup time + max 5 min when the job might start.
My expectation would be that beginning from the defined time, the job might be
executed. Only if the "repeat until" time has expired, it should be set to
invalid.
The problem is that the job starts correctly within this timeframe, but after
running for a while an event happens to abort it. When the scheduler reaches
"evaluateJobs()" in an attempt to restart it, the startup time has already
passed for a while and leads to the state "invalid".
Changing the behavior as described would make such jobs much more robust
against temporarily failures. Currently, when an abort happens after the 5 min,
the job will never start again.
--
You are receiving this mail because:
You are watching all bug changes.
