[ldv-project] [yandex.ru代发]Re: can not download ldv-docker-0.8.tar.gz
黄有焱
huangyy at landicorp.com
Fri Apr 5 07:56:02 MSK 2019
hi Evgeny Novikov
1: I get a new pc, the hardware satisfied with the requirement ,but i found the same result. klever is the lastest version. i clone it this morning.
[cid:_Foxmail.1 at 24115825-e388-4268-8f91-1ad3d3938980]
[cid:_Foxmail.1 at d0069c1e-c6bb-64fb-6b8d-b8106621cadf]
my new pc evironment
2:system
[cid:_Foxmail.1 at d1fb61c7-a10d-04cf-90a5-8e886a365aed]
3:memory and disk
[cid:_Foxmail.1 at 9e233cee-3f3a-cdd3-6bf8-451b081236ba]
[cid:_Foxmail.1 at b72fabf4-5786-aa35-fd95-bc7e7e899f46]
4: cpu
[cid:_Foxmail.1 at 11030079-8e69-c734-f284-0f98fee57b39]
[cid:_Foxmail.1 at 7509cb03-bc54-52c1-f78f-18e9e6865510]
5: Is there some thing changed the use method? I found some different on klever install directory. There is only one linux 3.14 project job on the new version,
[cid:_Foxmail.1 at b16b8444-a620-fe0e-3f3c-3406080a2817]
Could you help me to solve it?? Thanks!!!
Thanks and best regards
youyan
Fujian LANDI Commercial Equipment Co., Ltd
发件人： Evgeny Novikov<mailto:novikov at ispras.ru>
发送时间： 2019-04-02 15:24
收件人： 黄有焱<mailto:huangyy at landicorp.com>; khoroshilov<mailto:khoroshilov at ispras.ru>
抄送： ldv-project<mailto:ldv-project at linuxtesting.org>
主题： Re: [ldv-project] [yandex.ru代发]Re: can not download ldv-docker-0.8.tar.gz
Hi youyan,
it seems, you did not pay an attention to my note:
... Most important is your hardware. I hope that it meets https://klever.readthedocs.io/en/latest/deploy.html#hardware-requirements.<https://klever.readthedocs.io/en/latest/deploy.html#hardware-requirements.>
Klever needs computational resources not only for solving verification jobs (with help of Klever Core which you tried to configure), but for solving verification tasks by verification back-ends like CPAchecker. The latter needs much more CPU time and RAM. RAM is limited strictly unlike CPU time by your hardware. Of course you can edit file "tasks.json" presented at the job page (you should go to Job -> Edit for that), but with small values there you can obtain bad verification results.
So, for experiments you can specify less RAM in "tasks.json", but for production I recommend to use more powerful machine.
--
Evgeny Novikov
Linux Verification Center, ISP RAS
http://linuxtesting.org
02.04.2019, 09:30, "黄有焱" <huangyy at landicorp.com>:
hi khoroshilov
fellow is my test status now:
1: use manager username enter test view;
2: select linux 3.14 and enter sub view
[cid:_Foxmail.1 at e19ac2bb-fb3d-8455-d751-c927766904ae]
3: start with default value
[cid:_Foxmail.1 at ccfdb7f8-a395-9958-ed4a-d23938988faa]
the test result is fellow
[cid:_Foxmail.1 at ea5c4d65-e058-83e2-f98b-8cfc5cb428b3]
4: select start
[cid:_Foxmail.1 at 88d5c4de-0cf3-633a-f2ab-173fe062ac82]
Manual configuration
[cid:_Foxmail.1 at a1e19534-6c0a-f7a1-2d4a-8dbfabc0b348]
the test result is fellow:
5: My pc enviroment
[cid:_Foxmail.1 at 54127d6b-56d4-d57d-0eae-b45bf40f854e]
[cid:_Foxmail.1 at 8bae9c05-74be-498c-40c9-9b4cdf8d7480]
[cid:_Foxmail.1 at 32cd3aca-0e74-1adf-f80c-f3b04ed37b06]
I have not idea about how to solve the issue.Can you give me some info to me for fixing it? thanks!!!
Thanks and best regards
youyan
Fujian LANDI Commercial Equipment Co., Ltd
发件人： Evgeny Novikov<mailto:novikov at ispras.ru>
发送时间： 2019-03-29 13:03
收件人： 黄有焱<mailto:huangyy at landicorp.com>; khoroshilov<mailto:khoroshilov at ispras.ru>
抄送： ldv-project<mailto:ldv-project at linuxtesting.org>
主题： Re: [ldv-project] [yandex.ru代发]Re: can not download ldv-docker-0.8.tar.gz
Hi youyan,
29.03.2019, 04:37, "黄有焱" <huangyy at landicorp.com<mailto:huangyy at landicorp.com>>:
hi Evgeny Novikov
Thanking for your reply and help. Fellow is my enviroment and some issues info.
1: what version of Klever did you install?
I fetch klever by git clone --recursive https://forge.ispras.ru/git/klever.git,<https://forge.ispras.ru/git/klever.git,so> so it should on master branch.<https://forge.ispras.ru/git/klever.git, so%20it%20should%20on%20master%20branch.>
I see that in general everything is okay.
BTW, I detected a small but crucial issue in master that you will encounter if you will follow the standard workflow. So, I recommend you to update Klever according to documentation. It should be pretty simple and fast.
2:Collect the appropriate build base, met some error,attachment is the error log
[cid:_Foxmail.1 at 311943b3-d1dd-013d-8edd-c5898e4b6310]
The first issue is known, it is not critical at all. Perhaps, you just won't be able to verify some particular Linux kernel modules, but most likely you are not interested in verification of all modules.
We will investigate reasons of the second and the third issues (https://github.com/17451k/clade/issues/89). We did not see them before. I suggest that running clade-all with sudo will help to overcome them, but it is just a temporary workaround. I am not sure, but the issue seems to be rather critical, so, something can fail later.
3: My pc enviroment:
[cid:_Foxmail.1 at f56328ce-50d9-0368-448f-9e8740c0944e]
If I should switch to debian 9?
I think that there you will have the same issue. Most important is your hardware. I hope that it meets https://klever.readthedocs.io/en/latest/deploy.html#hardware-requirements.
4: I found that Klever 2.0 is only support x86 and x86_64.
[cid:_Foxmail.1 at b9c1a523-4807-0c5e-9b8f-8f33dd9897df]
Our projects are arm platform. Is there klever version can support arm platform on your hand? If have,can your release to me?
No, we did not have it and we need to update and to test several things since we made these experiments several years ago and everything moved ahead too much.
In Klever there are several add-ons<https://klever.readthedocs.io/en/latest/deploy-common.html#klever-addons> that care about a target software architecture more or less. Just CIF should be re-built appropriately as an ARM cross-compiler. Other add-ons need just specific configurations. Nevertheless, in general there can be some unexpected issues.
Thus, I recommend you to try to build and to verify your modules built for x86_64 if this is possible of course.
Thanks and best regards
youyan
Fujian LANDI Commercial Equipment Co., Ltd
发件人： Evgeny Novikov<mailto:novikov at ispras.ru>
发送时间： 2019-03-28 13:52
收件人： 黄有焱<mailto:huangyy at landicorp.com>; khoroshilov<mailto:khoroshilov at ispras.ru>
抄送： ldv-project<mailto:ldv-project at linuxtesting.org>
主题： [yandex.ru代发]Re: [ldv-project] can not download ldv-docker-0.8.tar.gz
Dear youyan,
we welcome your goal and we will be glad to help you.
First of all, I would like to know what version of Klever did you install? The latest version from the master branch should work pretty well, but there can be some new tricky issues regarding Klever 2.0 that is marked by tag v2.0 in the Git repository.
Unfortunately, either in Klever 2.0 or in the latest version of Klever we have not any user documentation except for deployment instructions. If your deployment was successful, you should be able to open localhost:8998 in your browser. There you can sign in with user manager (the password is the same as username) that has very many permissions except for user management. For the latter there is user admin (the password is the same as username).
After successful signing in, please, check that in Menu -> Schedulers the Klever scheduler is healthy.
Then you can try to start solution of verification job Linux 3.14. And you should see an error like "FileExistsError: Build base "/home/admin/klever-bin/klever/build bases/linux-3.14.79" is not a directory".
Below, please, find my previous answer regarding preparing sources for verification:
Now we do not provide source code of target programs to Klever directly, but prepare so called build bases in advance. To do that you need to do the following actions on a machine where you deployed Klever 2.0:
1. Get sources of required versions of the Linux kernel, e.g.:
$ wget https://cdn.kernel.org/pub/linux/kernel/v3.x/linux-3.14.79.tar.xz
$ tar -xf linux-3.14.79.tar.xz
$ cd linux-3.14.79
2. Configure the Linux kernel appropriately, e.g.:
$ make allmodconfig
3. Build the Linux kernel intercepting build commands, e.g.:
$ clade-intercept make -j16
(this can take several dozens of minutes)
4. Collect the appropriate build base:
PATH=$PATH:$KLEVER_DEPLOY_DIR/klever-addons/CIF/ clade-all -p linux_kernel cmds.txt
(this can take several hours, and unfortunately there can be some crucial errors somewhere in the middle since we did not test it much with new versions of the Linux kernel, but I hope that we can workaround all issues)
5. Execute this magic command:
echo "[\"$(readlink -f .)\"]" > "clade/Storage/working source trees.json"
You don't need to execute the last step for the latest Klever from the master branch.
Your build base is ready. It is placed into directory clade. You can rename this directory to something that you like more, e.g. to linux-3.14.79. Then you need to either specify an absolute path to this directory in job.json (option "build base") or install it using an appropriate deployment configuration and deployment scripts.
For new versions of the Linux kernel you will need to patch source files in subdirectory "Storage" within the build base.
After all you should be able to solve job "Linux 3.14".
If you will meet some issues, please, report them to us. We will try to solve or workaround them together.
At last, you can read and contribute Further development of Klever in favor of verification of the Linux kernel<https://docs.google.com/document/d/11e7cDzRqx0nO1UBcM75l6MS28zRBJUicXdNiReEpDKI/edit>, that describes many different issues with Klever.
--
Evgeny Novikov
Linux Verification Center, ISP RAS
http://linuxtesting.org<http://linuxtesting.org/>
28.03.2019, 07:36, "黄有焱" <huangyy at landicorp.com<mailto:huangyy at landicorp.com>>:
hi khoroshilov
it very kind of you for replying my email. I have already installed klever on my ubunut 18.04 PC.
But I don't know how to test my kernel module driver.Could you give me some steps or tip? make me
can startup klever, for improving our source code quality. thanks!!!
1:
2:
3
[cid:_Foxmail.1 at b3404b05-1c16-755c-0721-b3ce1e6af112]
Thanks and best regards
youyan
Fujian LANDI Commercial Equipment Co., Ltd
From: Alexey Khoroshilov<mailto:khoroshilov at ispras.ru>
Date: 2019-03-27 21:20
To: 黄有焱<mailto:huangyy at landicorp.com>
CC: ldv-project at linuxtesting.org<mailto:ldv-project at linuxtesting.org>
Subject: Re: can not download ldv-docker-0.8.tar.gz
Dear huangyy,
Thank you for the report.
We have updated the link to the LDV image:
http://sed.ispras.ru/fmprac/data/ldv-docker-0.8.tar.gz
But as you may know, we switched from LDV Tools to the next generation toolset that is called KLEVER:
https://forge.ispras.ru/projects/klever
A draft of documentation for KLEVER is available here:
https://klever.readthedocs.io/en/latest/
Best regards,
Alexey Khoroshilov
Linux Verification Center, ISPRAS
On 27.03.2019 4:31, 黄有焱 wrote:
hi
I want to download LDV Tools 0.8 docker,but failed. access the web url,the result is fellow
[cid:_Foxmail.1 at 2723c899-cb2f-b44f-ac29-15151e7f67bc]
could you help me solve the it?or tell me,how can I download the archiver?Thanks!!! looking forward to your reply.
________________________________
黄有焱
,
_______________________________________________
ldv-project mailing list
ldv-project at linuxtesting.org<mailto:ldv-project at linuxtesting.org>
http://linuxtesting.org/cgi-bin/mailman/listinfo/ldv-project
,
_______________________________________________
ldv-project mailing list
ldv-project at linuxtesting.org<mailto:ldv-project at linuxtesting.org>
http://linuxtesting.org/cgi-bin/mailman/listinfo/ldv-project
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://linuxtesting.org/pipermail/ldv-project/attachments/20190405/857ea885/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Catch9703(04-05-(04-05-12-55-45).jpg
Type: image/jpeg
Size: 85652 bytes
Desc: Catch9703(04-05-(04-05-12-55-45).jpg
URL: <http://linuxtesting.org/pipermail/ldv-project/attachments/20190405/857ea885/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: InsertPic_ACED(0(04-05-12-55-45).png
Type: image/png
Size: 17917 bytes
Desc: InsertPic_ACED(0(04-05-12-55-45).png
URL: <http://linuxtesting.org/pipermail/ldv-project/attachments/20190405/857ea885/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Catch(04-05-12-3(04-05-12-55-45).jpg
Type: image/jpeg
Size: 55340 bytes
Desc: Catch(04-05-12-3(04-05-12-55-45).jpg
URL: <http://linuxtesting.org/pipermail/ldv-project/attachments/20190405/857ea885/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: CatchEADA(04-05-(04-05-12-55-45).jpg
Type: image/jpeg
Size: 42911 bytes
Desc: CatchEADA(04-05-(04-05-12-55-45).jpg
URL: <http://linuxtesting.org/pipermail/ldv-project/attachments/20190405/857ea885/attachment-0002.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: CatchD3EB(04-05-(04-05-12-55-45).jpg
Type: image/jpeg
Size: 89986 bytes
Desc: CatchD3EB(04-05-(04-05-12-55-45).jpg
URL: <http://linuxtesting.org/pipermail/ldv-project/attachments/20190405/857ea885/attachment-0003.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: CatchECBB(04-05-(04-05-12-55-45).jpg
Type: image/jpeg
Size: 28735 bytes
Desc: CatchECBB(04-05-(04-05-12-55-45).jpg
URL: <http://linuxtesting.org/pipermail/ldv-project/attachments/20190405/857ea885/attachment-0004.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Catch548B(04-05-(04-05-12-55-45).jpg
Type: image/jpeg
Size: 66496 bytes
Desc: Catch548B(04-05-(04-05-12-55-45).jpg
URL: <http://linuxtesting.org/pipermail/ldv-project/attachments/20190405/857ea885/attachment-0005.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: InsertPic_(04-05(04-05-12-55-45).png
Type: image/png
Size: 15890 bytes
Desc: InsertPic_(04-05(04-05-12-55-45).png
URL: <http://linuxtesting.org/pipermail/ldv-project/attachments/20190405/857ea885/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Catch775D(04-05-(04-05-12-55-45).jpg
Type: image/jpeg
Size: 53602 bytes
Desc: Catch775D(04-05-(04-05-12-55-45).jpg
URL: <http://linuxtesting.org/pipermail/ldv-project/attachments/20190405/857ea885/attachment-0006.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Catch12BC(04-05-(04-05-12-55-45).jpg
Type: image/jpeg
Size: 54839 bytes
Desc: Catch12BC(04-05-(04-05-12-55-45).jpg
URL: <http://linuxtesting.org/pipermail/ldv-project/attachments/20190405/857ea885/attachment-0007.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Catch30B0(04-05-(04-05-12-55-45).jpg
Type: image/jpeg
Size: 43787 bytes
Desc: Catch30B0(04-05-(04-05-12-55-45).jpg
URL: <http://linuxtesting.org/pipermail/ldv-project/attachments/20190405/857ea885/attachment-0008.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: InsertPic_C7B7(0(04-05-12-55-45).png
Type: image/png
Size: 40598 bytes
Desc: InsertPic_C7B7(0(04-05-12-55-45).png
URL: <http://linuxtesting.org/pipermail/ldv-project/attachments/20190405/857ea885/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: InsertPic_3695(0(04-05-12-55-45).png
Type: image/png
Size: 34069 bytes
Desc: InsertPic_3695(0(04-05-12-55-45).png
URL: <http://linuxtesting.org/pipermail/ldv-project/attachments/20190405/857ea885/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: InsertPic_A881(0(04-05-12-55-45).png
Type: image/png
Size: 10177 bytes
Desc: InsertPic_A881(0(04-05-12-55-45).png
URL: <http://linuxtesting.org/pipermail/ldv-project/attachments/20190405/857ea885/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: InsertPic_8A47(0(04-05-12-55-45).png
Type: image/png
Size: 23838 bytes
Desc: InsertPic_8A47(0(04-05-12-55-45).png
URL: <http://linuxtesting.org/pipermail/ldv-project/attachments/20190405/857ea885/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: InsertPic_6401(0(04-05-12-55-45).png
Type: image/png
Size: 179904 bytes
Desc: InsertPic_6401(0(04-05-12-55-45).png
URL: <http://linuxtesting.org/pipermail/ldv-project/attachments/20190405/857ea885/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: InsertPic_D7F0(0(04-05-12-55-45).png
Type: image/png
Size: 23941 bytes
Desc: InsertPic_D7F0(0(04-05-12-55-45).png
URL: <http://linuxtesting.org/pipermail/ldv-project/attachments/20190405/857ea885/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: InsertPic_B1D0(0(04-05-12-55-45).png
Type: image/png
Size: 31898 bytes
Desc: InsertPic_B1D0(0(04-05-12-55-45).png
URL: <http://linuxtesting.org/pipermail/ldv-project/attachments/20190405/857ea885/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: InsertPic_(03-28(04-05-12-55-45).png
Type: image/png
Size: 44099 bytes
Desc: InsertPic_(03-28(04-05-12-55-45).png
URL: <http://linuxtesting.org/pipermail/ldv-project/attachments/20190405/857ea885/attachment-0009.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: InsertPic_554A(0(04-05-12-55-45).png
Type: image/png
Size: 58859 bytes
Desc: InsertPic_554A(0(04-05-12-55-45).png
URL: <http://linuxtesting.org/pipermail/ldv-project/attachments/20190405/857ea885/attachment-0010.png>
More information about the ldv-project
mailing list