D22446: Adding error handling strategy control to Scheduler

[Eric Dejouhanet]

TallFurryMan added a comment.


  > Hm, quite complicated. Has this ever worked?
  
  That specific issue, that is, completed jobs resetting to scheduled, yes it has. That was part of my tests in 2017.
  
  > Nevertheless, I think when running multi-day-schedules, I would use "Remember job progress". In that case I think this situation would not happen.
  
  Agreed, and I confirm it worked yesterday. We have other problems with that option, but in that "simple" case of a mosaic, it is a good workaround.
  
  > What is quite good visible from your example, that setting jobs to completed when they hit a constraint is not a good idea. Complete means that the defined amount of frames have been taken - nothing else.
  > 
  > Therefore I would like to proceed in that direction.
  
  I agree. It is a regression from this diff, isn't it?
  
  > Meanwhile, it would be great if we find a way to simulate the regression above in a reasonable timeframe.
  
  I very quickly checked the code against my test case, and I'm still puzzled why the situation is different when scheduler is running and looks for a new job (before sleeping in my log) and when scheduler wakes up and looks for a new job. I'll have to check again, slowly this time. I think the observatory shutdown has a role in there.

REPOSITORY
  R321 KStars

REVISION DETAIL
  https://phabricator.kde.org/D22446

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