Project

General

Profile

Feature #9164

Updated by Evgeny Novikov almost 6 years ago

Sometimes we observed the following reason for failed tasks and jobs: tasks: 
 <pre> 
 2018-07-25 14:39:56 (components.py:435) RP ERROR> Raise exception: 
 Traceback (most recent call last): 
   File "/var/lib/klever/workspace/Branches-and-Tags-Processing/src/core/core/components.py", line 428, in run 
     self.main() 
   File "/var/lib/klever/workspace/Branches-and-Tags-Processing/src/core/core/components.py", line 332, in callbacks_caller 
     ret = attr(*args, **kwargs) 
   File "/var/lib/klever/workspace/Branches-and-Tags-Processing/src/core/core/vrp/__init__.py", line 250, in fetcher 
     raise RuntimeError('Failed to decide verification task: {0}'.format(self.task_error)) 
 RuntimeError: Failed to decide verification task: Execution of task 758 terminated with an exception: 2018-07-25 14:39:48,786 - WARNING - CPU throttled itself during benchmarking due to overheating. Benchmark results are unreliable! 
 </pre> 
 We definitely need to ignore this. 

 For example I attached a directory of a failed task. One can see that everything is okay except for several warnings from BenchExec.

Back