Project

General

Profile

Feature #8483

Avoid using BenchExec from within Core

Added by Evgeny Novikov over 1 year ago. Updated about 1 year ago.

Status:
Closed
Priority:
Urgent
Assignee:
Category:
Infrastructure of Core
Target version:
Start date:
10/06/2017
Due date:
% Done:

0%

Estimated time:
Published in build:

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.

History

#1 Updated by Ilja Zakharov over 1 year ago

It also kills Cil and CIF if they use too much resources, so it is not a good idea to replace it.

#2 Updated by Evgeny Novikov over 1 year ago

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.

#3 Updated by Ilja Zakharov about 1 year ago

  • Target version set to 1.0
  • Priority changed from High to Urgent
  • Assignee set to Ilja Zakharov
  • Status changed from New to Open

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.

#4 Updated by Ilja Zakharov about 1 year ago

  • Status changed from Open to Resolved

All works as expected. The branch also contains backported fixes to avoid jobs corruption.

#5 Updated by Evgeny Novikov about 1 year ago

  • 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