Feature #6618
closed
Not all restrictions of verification tasks are passed to BenchExec
Added by Evgeny Novikov almost 9 years ago.
Updated over 7 years ago.
Description
For instance, it seems that CPAchecker can use all cores rather than the default number of them (2 at the moment).
- Assignee set to Ilja Zakharov
- Priority changed from High to Urgent
This issue should be fixed together with other scheduling deadlock issues.
- Tracker changed from Bug to Feature
With a new resource manager all restrictions can be passed to BenchExec. But currently there are two problems rest unsolved:
- BenchExec and RunExec have different API to set CPU cores and for us the better option is to provide particular core identifiers and this should be implemented in BenchExec.
- Without container mode BenchExec and RunExec do not restrict disk space so we should switch to it.
- Status changed from New to Resolved
Implemented in be-advanced-integration.
- Status changed from Resolved to Closed
Also available in: Atom
PDF