Feature #8446

Feature #8149: Think on proper progress evaluation when several jobs are solved at once or/and much computational resources are available

Fix and improve progress reporting

Added by Evgeny Novikov 2 months ago. Updated 9 days ago.

Status:ClosedStart date:10/10/2017
Priority:UrgentDue date:
Assignee:Ilja Zakharov% Done:


Category:-Spent time:-
Target version:0.3
Published in build:


Several Core components should be fixed and improved to get meaningful progress after all.


Feature #8491: Update the progress reporting implementation in BridgeRejected

Related issues

Related to Klever - Feature #7470: Add support for user-oriented time limit New 08/15/2016
Related to Klever - Feature #7223: Use Klever extensions to Python multiprocessing for deci... Closed 05/19/2016


#1 Updated by Evgeny Novikov about 1 month ago

  • Assignee set to Ilja Zakharov

#2 Updated by Ilja Zakharov 15 days ago

  • Status changed from New to Resolved

Implemented in 8149-new-progress.

#3 Updated by Ilja Zakharov 15 days ago

  • Status changed from Resolved to Open

Need to update the implementation according to the last changes in the documentation of the feature.

#4 Updated by Ilja Zakharov 13 days ago

  • Status changed from Open to Resolved

The implementation is updated.

#5 Updated by Evgeny Novikov 9 days ago

  • Status changed from Resolved to Closed

After fixing several issues I merged the branch to master in commit:459f75e7.

Also available in: Atom PDF