https://bugs.kde.org/show_bug.cgi?id=492930
Bug ID: 492930
Summary: Race when scheduler goes to next sequence in a group
Classification: Applications
Product: kstars
Version: git
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: mutla...@ikarustech.com
Reporter: co...@mimas.ru
Target Milestone: ---
Created attachment 173514
--> https://bugs.kde.org/attachment.cgi?id=173514&action=edit
Log
The exact misbehavior varies depending on machine, devices, etc. For
demonstration, I compiled current version from git and setup a local INDI
profile with telescope and camera simulators only. Sequence and schedule files
are attached.
The sequence is simply 3 exposures. The schedule has 3 different targets
sharing one Group name, the same sequence.
I expect to get a clean indefinite loop of 3 images of each target.
Instead, for each iteration, it captures and saves 4 images and starts fifth
which is then aborted and reported as an error.
In my real observatory, depending on timing, I may get 3 images within each job
captures and actually saved, but the last one is 'aborted'. Scheduler marks job
as failed, waits 60s (per configuration), then proceeds to the next job.
Sometimes it is all fine, 3 successful images and immediate jump to the next
job.
I did not see this problem with 3.7.0. As I started upgrading to 3.7.2, it
appeared.
I don't see this kind of issues with jobs not in a group, even if there are
other grouped jobs in the same schedule. Of course, all this story is with
Greedy Scheduler enabled.
--
You are receiving this mail because:
You are watching all bug changes.
