Project

General

Profile

Actions
Copy link

Feature #8483

closed

Avoid using BenchExec from within Core

Added by Evgeny Novikov about 7 years ago. Updated almost 7 years ago.

Status:
Closed
Priority:
Urgent
Assignee:
Ilja Zakharov
Category:
Infrastructure of Core
Target version:
1.0
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.

Actions
Copy link
 #1

Updated by Ilja Zakharov about 7 years ago

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

Actions
Copy link
 #2

Updated by Evgeny Novikov about 7 years 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.

Actions
Copy link
 #3

Updated by Ilja Zakharov almost 7 years ago

  • 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.

Actions
Copy link
 #4

Updated by Ilja Zakharov almost 7 years ago

  • Status changed from Open to Resolved

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

Actions
Copy link
 #5

Updated by Evgeny Novikov almost 7 years 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).

Actions
Copy link

Also available in: Atom PDF