D14942: Connect new-image event to Scheduler imaging time estimator.

Wolfgang Reissenberger noreply at phabricator.kde.org
Wed Aug 29 13:40:33 BST 2018

wreissenberger added a comment.

  In D14942#317072 <https://phabricator.kde.org/D14942#317072>, @wreissenberger wrote:
  > I did some tests, looks good. There is one test that already failed in D14684 <https://phabricator.kde.org/D14684> and is still present. It might be exotic, but it leads to continuous looping.
  > The setup is the following: create a schedule with two jobs for the same target with the same sequence job (say 1xLum for example). The first job starts and captures the first frame.
  > And here is where the problem occurs: now calling //Scheduler::updateCompletedJobsCount()// detects the one frame, but when evaluating the second job (which did not run yet), the value in the captured frames map is overwritten. This leads to an endless loop of the first job.
  The fix is quite simple. Here is the patch:F6223164: looping.patch <https://phabricator.kde.org/F6223164>

  R321 KStars

  improve__scheduler_image_update (branched from master)


To: TallFurryMan, mutlaqja, wreissenberger
Cc: kde-edu, narvaez, apol
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-edu/attachments/20180829/6025a796/attachment.html>

More information about the kde-edu mailing list