Project

General

Profile

Actions

Bug #6616

closed

Remove enumerating of verifiers from native tasks worker configuration

Added by Evgeny Novikov almost 9 years ago. Updated about 8 years ago.

Status:
Closed
Priority:
Urgent
Assignee:
Category:
Scheduling
Target version:
-
Start date:
01/29/2016
Due date:
% Done:

0%

Estimated time:
Detected in build:
svn
Platform:
Published in build:

Description

This actually should be done in native scheduler configuration. Respectively usage of these configurations should be updated.


Related issues 1 (0 open1 closed)

Blocks Klever - Feature #6699: Native scheduler does not take care of verifier versionClosedIlja Zakharov02/02/2016

Actions
Actions #1

Updated by Evgeny Novikov over 8 years ago

  • Assignee set to Ilja Zakharov
  • Priority changed from High to Urgent

Raise the priority as of the blocked issue.

Actions #2

Updated by Ilja Zakharov about 8 years ago

  • Status changed from New to Resolved

Done at branch 'scheduler_verifier_versions'.

Actions #3

Updated by Evgeny Novikov about 8 years ago

  • Status changed from Resolved to Closed

I merged the given branch to master in 5bcde97.

Here is a comment from Ilja's commit describing what one should do now:

Now one should specify its own installed verification tools and versions and specify them at scheduler task client configuration. The configuration file is updated dynamically.

From now several versions of CPAchecker can be specified and used simultaneously.

Besides NativeScheduler started to report available verification tools and their versions to Bridge, so one can examine what verifiers can be used (Menu -> Schedulers -> Klever) when comprising new jobs.

Several sanity checks refuse related mistakes in the task client configuration and in verification tasks.

Actions

Also available in: Atom PDF