[ldv-project] Unexpected errors occur when running Klever according to the tutorial

[Tuo Li]

Dear Pavel,

Thank you for your suggestions! They work well!

By the way, I run Klever with "concurrency safety" specifications, but it
seems that CPALockator is not enabled.

[image: image.png]

I wonder whether my configuration file is proper, or if there is something
else I missed.

Here is the job.json file:

{
> "project": "Linux",
> "build base": "/home/lt/Work/klever/build-base-linux-5.5.19-allmodconfig",
> "targets": [
> "drivers/usb/**"
> ],
> "specifications set": "5.5",
> "requirement specifications": [
> "concurrency safety"
> ]
> }


Thank you very much!

Sincerely,
Tuo Li

On Mon, Oct 16, 2023 at 4:08 PM Павел <andrianov at ispras.ru> wrote:

> Dear Tuo Li,
>
> To deal with the first error (memory limit) you may also decrease
> parallelism. In job start settings by default 3-4 plugins (EMG, CIF) are
> run in parallel. Just for experiment you may run everything sequentially.
> Also you may increase memory limits in the same settings menu, in the right
> column.
>
> To deal with the second issue (scheduler reset), you just need to restart
> scheduler: sudo service klever-native-scheduler restart. Also, one bug
> related to the issue was fixed some time ago. So, it is make sense to
> update Klever - 'update' command just updates the tool and do not affect
> any results, marks and so on.
> Best regards,
> Pavel
>
> 15.10.2023 12:57, Tuo Li пишет:
>
> Hi,
>
> I have tried to run Klever according to the tutorial but some errors
> occurred.
>
> The configure file job.json is like this:
>
> {
>>   "project": "Linux",
>>   "build base":
>> "/home/lt/Work/klever/build-base-linux-5.5.19-allmodconfig",
>>   "targets": [
>>     "drivers/usb/**"
>>   ],
>>   "specifications set": "5.5",
>>   "requirement specifications": [
>>     "drivers:clk.*",
>>     "memory safety"
>>   ]
>> }
>>
>
> However, when I created and started the decision with default
> configuration,
> a memory error is thrown in the website:
>
> Process was terminated since it ran out of memory (you may need to adjust
>> job solution settings)
>
>
> Then I tried creating and starting the decision with custom configuration
> according to
> my experimental environment.
> I set the memory size to 32.0 GB, and the number of CPU cores to 4, and
> then
> started the decision again, but I got another error:
>
> Scheduler has been terminated or reset
>
>
> I have tried many configurations but still can not fix these problems.
>  Any feedback will be appreciated!
>
> Sincerely,
> Tuo Li
>
>
>
> _______________________________________________
> ldv-project mailing listldv-project at linuxtesting.orghttp://linuxtesting.org/cgi-bin/mailman/listinfo/ldv-project
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://linuxtesting.org/pipermail/ldv-project/attachments/20231019/135b82d9/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 58236 bytes
Desc: not available
URL: <http://linuxtesting.org/pipermail/ldv-project/attachments/20231019/135b82d9/attachment.png>