Bug 394379 - Scheduler stops progress after the first job is complete
Summary: Scheduler stops progress after the first job is complete
Status: RESOLVED NOT A BUG
Alias: None
Product: kstars
Classification: Applications
Component: general (show other bugs)
Version: git
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Jasem Mutlaq
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-17 16:03 UTC by Csaba Kertész
Modified: 2018-05-17 20:58 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Scheduler screenshot (74.73 KB, image/png)
2018-05-17 16:03 UTC, Csaba Kertész 		Details
Scheduler log (3.91 KB, text/plain)
2018-05-17 16:04 UTC, Csaba Kertész 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Csaba Kertész 2018-05-17 16:03:39 UTC 
Created attachment 112711 [details]
Scheduler screenshot

I have three jobs in the scheduler and it used to work before, but some recent changes broke the scheduling. After the first job was completed, the next job was not started in my previous night. The scheduler selected the first job again after it was completed and everything stopped. Any advice is appropriated what could be the cause of this problem.

A screenshot and a scheduler log is attached.
Comment 1 Csaba Kertész 2018-05-17 16:04:46 UTC 
Created attachment 112712 [details]
Scheduler log
Comment 2 Csaba Kertész 2018-05-17 16:06:24 UTC 
An other comment that the same jobs used to work properly in the past. It always loaded from disk.
Comment 3 Jasem Mutlaq 2018-05-17 20:34:25 UTC 
Eric told me this was fixed in https://phabricator.kde.org/D12930

Are you having this problem from master?
Comment 4 Csaba Kertész 2018-05-17 20:58:03 UTC 
Ok. Cool