Project

General

Profile

Actions

Feature #8379

open

Properly process wall time outs

Added by Evgeny Novikov over 7 years ago. Updated over 6 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
08/23/2017
Due date:
% Done:

0%

Estimated time:
Published in build:

Description

At the moment corresponding verification task decisions are terminated with errors like:

Execution of task 3592 terminated with an exception: 2017-08-23 06:09:08,581 - WARNING - Killing process 15571 due to wall time timeout.

This results in verification reports are absent that is no logs, no resources consumption, no input verifier files.

I suppose to process wall time outs like time outs. So don't forget to add a corresponding unknowns preset mark.


Related issues 1 (0 open1 closed)

Related to Klever - Feature #8380: Specify greater wall time limitsClosedIlja Zakharov08/23/2017

Actions
Actions #1

Updated by Evgeny Novikov over 7 years ago

BTW, I observed just about 0.05% of such the failure when verified all modules of the Linux kernel and didn't observe it during testing and validation. So, the issue isn't very important.

Actions #2

Updated by Evgeny Novikov about 7 years ago

  • Priority changed from High to Urgent
  • Target version set to 2.0

But for some heavyweight rules the number of wall timeouts can be really great. Wall timeouts often happen at OpenStack instances where virtual CPUs are highly overloaded.

Actions #3

Updated by Evgeny Novikov over 6 years ago

  • Target version changed from 2.0 to 1.1

This issue is not strictly bound with purposes of 2.0 that targets verification of C software.

Actions #4

Updated by Evgeny Novikov over 6 years ago

  • Assignee deleted (Ilja Zakharov)
  • Priority changed from Urgent to Normal
  • Target version deleted (1.1)

After #8380 no normal users will likely observe wall timeouts. So there is very little sense to do this task.

Actions

Also available in: Atom PDF