Project

General

Profile

Feature #8380

Specify greater wall time limits

Added by Evgeny Novikov almost 2 years ago. Updated 12 months ago.

Status:
Closed
Priority:
Urgent
Assignee:
Category:
Scheduling
Target version:
Start date:
08/23/2017
Due date:
% Done:

0%

Estimated time:
Published in build:

Description

At the moment wall time limits are almost the same as CPU time limits which isn't great at all.

Unfortunately this can't be implemented via benchmarks due to this issue.


Files

Job-78a7548984.zip (10 MB) Job-78a7548984.zip Evgeny Novikov, 07/27/2018 12:22 AM

Related issues

Related to Klever - Feature #8379: Properly process wall time outsNew08/23/2017

Actions

History

#1

Updated by Evgeny Novikov over 1 year ago

  • Priority changed from High to Urgent

BTW, because of this issue I got wall timeouts for verification tasks requiring ~7.5 minutes of CPU time with timelimit equal to 15 minutes. This depends on a server load and hardware characteristics, but this is very bad from the benchmarking point of view. We need to find any solution. Perhaps we can disable wall timeouts in BenchExec and enforce them in scheduler workers ourselves.

#2

Updated by Evgeny Novikov over 1 year ago

  • Target version set to 2.0
#3

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

#4

Updated by Ilja Zakharov about 1 year ago

  • Status changed from New to Resolved

Implemented in 6614-speculative-scheduling.

#5

Updated by Evgeny Novikov about 1 year ago

  • Status changed from Resolved to Open

There is little sense to proceed to testing and for merging this branch to master as it needs again a way to install and to configure non-standard versions of BenchExec. I won't be surprised if everything will fail with current automatic deployments.

#6

Updated by Ilja Zakharov 12 months ago

  • Status changed from Open to Resolved

It is implemented now.

#7

Updated by Evgeny Novikov 12 months ago

CI detects predictable changes in associations for unknown marks for the validation job. Marks with following identifiers:
  • ef86f4f2d3ca1c1df0344dbc89d830f6,
  • 0d990ceb2317b87546c35448b3635305,
  • c450089f71843085027c5f38f9796a63,
  • f0a889ca491447c356784de52b21520c,
  • f4a68caa2c6b9c490e93591c21e0bbb1,
  • 789b222612c061dc0d8286eb19de1fd1,
  • c15112fddae7c4509ad639b4800a369c,
  • f0ba941f62e7fdadd76dad4cd93c1893

lost their relations with unknown reports at all, while there is one new associated mark 94cda75e1c23421736e612ef4131c545 (normal CPU timeout).

This changes are because BenchExec allows to detect CPU timeouts in the way we need.

To fix new issues, please, see at the attached job archive.

#8

Updated by Ilja Zakharov 12 months ago

  • Status changed from Open to Resolved

Fixed.

#9

Updated by Evgeny Novikov 12 months ago

  • Status changed from Resolved to Closed

Now everything works! I merged the branch to master in aa70aed85.

Also available in: Atom PDF