Feature #8371

Allow to specify units for computational resource limits

Added by Evgeny Novikov about 3 years ago. Updated about 3 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:
Published in build:


To enforce computational resource limits we use BenchExec which supported units even in version 1.7 we used before recent changes. Our format allows to specify limits for verification tasks just in bytes and milliseconds which isn't convenient. Limits for verification jobs can be specified in a Bridge form where unit GB is for memory and min is for time (both numbers are floats) - I think that can be remained as is.

To keep backward compatibility I suppose to still interpret limits without units as bytes and milliseconds for memory and time correspondingly.

Related issues

Related to Klever - Bug #8370: Fix CPU time limits for tasksClosed08/19/2017




Updated by Evgeny Novikov about 3 years ago

Please, see my comments about time limits for verification jobs in


Updated by Evgeny Novikov about 3 years ago

  • Assignee deleted (Ilja Zakharov)
  • Priority changed from Urgent to High

This issue does not have such the high priority.


Updated by Ilja Zakharov about 3 years ago

  • Status changed from New to Resolved
  • Assignee set to Ilja Zakharov
  • Priority changed from High to Urgent

Implemented in core-refactoring.

I have done it as I required this for further refactoring issues. Currently, tasks.json and a configuration of a scheduler node file are allowed to contain values with explicit units for memory- and time-related entries.


Updated by Evgeny Novikov about 3 years ago

  • Category deleted (Tasks generation)
  • Target version set to 0.2

Good news that soon we will enjoy this at last!

Indeed various places and components were affected by this feature implementation.


Updated by Evgeny Novikov about 3 years ago

  • Status changed from Resolved to Closed

I merged the branch to master in aec48ac1.

Also available in: Atom PDF