Feature #8483
closed
Avoid using BenchExec from within Core
Added by Evgeny Novikov about 7 years ago.
Updated almost 7 years ago.
Category:
Infrastructure of Core
Description
At the moment BenchExec is used to restrict computational resources consumption by third-party tools that can behave abnormally. Just CIL is restricted from Core with BenchExec.
I suppose to use more simple solution, namely Python module resource, that is already used to calculate computational resources consumption by Core and its components.
It also kills Cil and CIF if they use too much resources, so it is not a good idea to replace it.
Ilja Zakharov wrote:
It also kills Cil and CIF if they use too much resources, so it is not a good idea to replace it.
It is used just for CIL.
- Status changed from New to Open
- Assignee set to Ilja Zakharov
- Priority changed from High to Urgent
- Target version set to 1.0
As it seems to be critical at verifying new kernels lets do it a bit earlier.
I have implemented it in the branch rm-fix, so after testing I hope it will be soon resolved.
- Status changed from Open to Resolved
All works as expected. The branch also contains backported fixes to avoid jobs corruption.
- Status changed from Resolved to Closed
I merged the branch to master in 561ccab. So, we will not have these tricky issues from nested BenchExec (I am not sure that it was developed in this way ever).
Also available in: Atom
PDF