Feature #7435
closedSupport of several verifiers is required
0%
Description
Currently Klever supports only 1 hard-coded verifier:
"cpachecker location": "..."
and it is impossible to use several verifiers (or different versions of one).
For example, tests for rule specifications should be passed on all supported verifiers and for all existed models (such as property automata and instrumentation), therefore, in general case test job file should be working with different verifiers.
It is suggested to support the following format in configuration:
"verifiers": [
[
{"Alias": "..."},
{"location": "..."}
],
...
[
{"Alias": "..."},
{"location": "..."}
]]
Then it would be possible to use the required verifier in job file by its alias:
"verifier": {
"name": <verifier alias>,
...
Updated by Evgeny Novikov over 8 years ago
- Priority changed from High to Normal
This looks like hot plugging of verifiers without manual editing a NativeScheduler configuration and its restart. But as Ilja properly noted NativeScheduler isn't actually intended for production - it should be used just for development locally. Thus we should take care about this when developing Cluster/CloudScheduler.
Updated by Vitaly Mordan over 8 years ago
- Status changed from New to Resolved
The suggested solution was implemented in branch new_format_of_strategies.
Note, that it does not support verifier cloud (only native scheduler) and is intended for experiments. By default the old format is used.
Updated by Evgeny Novikov almost 5 years ago
- Status changed from Resolved to Rejected