How to use kci_test?

How to use kci_test?

[leimaohui]

Hi, all

I am learning to use kernelci. At present, I have installed kernelci docker and lava docker, and use kci_ build builds the kernel.
Using kci_test, we encountered some problems:

1. What do I need to do to connect kernelci and lava before the test command?

2. Is the following understanding of kci_test's options correct​?
For example:
./kci_test generate

  --bmeta-json=linux/_install_/bmeta.json \      //bmeta file in build directory generated by kci_build
  --dtbs-json=linux/_install_/dtbs.json \             //dtbs file in build directory generated by kci_build​
  --plan=baseline_qemu \                                      // test_plan        
  --target=qemu_arm64-virt-gicv3 \                     //device_type
  --lab=lab-name \                                                   //lab name which is recorded in lab-configs.yaml 
 --user=kernelci-user-name \                               //user of lava for kernelci test
  --token=abcd-7890 \                                            //token of lava user for kenelci test
  --lab-json=lab-name.json \                                  //JSON file generated by executing command get_lab_info
  > job.yaml

3. Error is occurred when executing the following command. Is there any problem with parameter specification?
Command line : $. / KCI_ test get_ lab_ info --lab=lab-linaro-lkft --lab-json=lab-linaro- lkft.json
Error message:   $ attributeerror: 'nonetype' object has no attribute 'scheduler'

Best regards
Lei Maohui

Re: How to use kci_test?

[leimaohui]

ping


________________________________________
From: kernelci@groups.io <kernelci@groups.io> on behalf of leimaohui <leimaohui@cn.fujitsu.com>
Sent: Monday, 22 June 2020 11:10
To: kernelci@groups.io
Subject: How to use kci_test?

Hi, all

I am learning to use kernelci. At present, I have installed kernelci docker and lava docker, and use kci_ build builds the kernel.
Using kci_test, we encountered some problems:

1. What do I need to do to connect kernelci and lava before the test command?

2. Is the following understanding of kci_test's options correct​?
For example:
./kci_test generate

  --bmeta-json=linux/_install_/bmeta.json \      //bmeta file in build directory generated by kci_build
  --dtbs-json=linux/_install_/dtbs.json \             //dtbs file in build directory generated by kci_build​
  --plan=baseline_qemu \                                      // test_plan
  --target=qemu_arm64-virt-gicv3 \                     //device_type
  --lab=lab-name \                                                   //lab name which is recorded in lab-configs.yaml
 --user=kernelci-user-name \                               //user of lava for kernelci test
  --token=abcd-7890 \                                            //token of lava user for kenelci test
  --lab-json=lab-name.json \                                  //JSON file generated by executing command get_lab_info
  > job.yaml

3. Error is occurred when executing the following command. Is there any problem with parameter specification?
Command line : $. / KCI_ test get_ lab_ info --lab=lab-linaro-lkft --lab-json=lab-linaro- lkft.json
Error message:   $ attributeerror: 'nonetype' object has no attribute 'scheduler'

Best regards
Lei Maohui

Re: How to use kci_test?

[Corentin Labbe]

On Mon, Jun 22, 2020 at 03:10:31AM +0000, leimaohui wrote:
> Hi, all
> 
> I am learning to use kernelci. At present, I have installed kernelci docker and lava docker, and use kci_ build builds the kernel.
> Using kci_test, we encountered some problems:
> 
> 1. What do I need to do to connect kernelci and lava before the test command?
> 

Hello

You need to create a lab in kernelci, you can use https://github.com/kernelci/kernelci-admin for this
With this lab created, you will have a token for it.

For LAVA, you need to have a LAVA instance working with a qemu passing healthcheck.
Then you need to create an user and get the token of it.


> 2. Is the following understanding of kci_test's options correct​?
> For example:
> ./kci_test generate
> 
>   --bmeta-json=linux/_install_/bmeta.json \      //bmeta file in build directory generated by kci_build
>   --dtbs-json=linux/_install_/dtbs.json \             //dtbs file in build directory generated by kci_build​
>   --plan=baseline_qemu \                                      // test_plan        
>   --target=qemu_arm64-virt-gicv3 \                     //device_type
>   --lab=lab-name \                                                   //lab name which is recorded in lab-configs.yaml 
>  --user=kernelci-user-name \                               //user of lava for kernelci test
>   --token=abcd-7890 \                                            //token of lava user for kenelci test
>   --lab-json=lab-name.json \                                  //JSON file generated by executing command get_lab_info
>   > job.yaml
> 

With all users/token and labname created in 1), it will works (generated some jobs in a directory "$labname"

> 3. Error is occurred when executing the following command. Is there any problem with parameter specification?
> Command line : $. / KCI_ test get_ lab_ info --lab=lab-linaro-lkft --lab-json=lab-linaro- lkft.json
> Error message:   $ attributeerror: 'nonetype' object has no attribute 'scheduler'
> 

Probably some user/token are wrong

Regards

Re: How to use kci_test?

[Guillaume Tucker]

On 28/06/2020 07:38, Corentin Labbe wrote:
> On Mon, Jun 22, 2020 at 03:10:31AM +0000, leimaohui wrote:
>> Hi, all
>>
>> I am learning to use kernelci. At present, I have installed kernelci docker and lava docker, and use kci_ build builds the kernel.
>> Using kci_test, we encountered some problems:
>>
>> 1. What do I need to do to connect kernelci and lava before the test command?
>>
> 
> Hello
> 
> You need to create a lab in kernelci, you can use https://github.com/kernelci/kernelci-admin for this
> With this lab created, you will have a token for it.
> 
> For LAVA, you need to have a LAVA instance working with a qemu passing healthcheck.
> Then you need to create an user and get the token of it.

As you've installed LAVA Docker, you should have a local LAVA
lab.  You need to create an API token for it with a user
called "kernel-ci".  Then as you have a KernelCI Docker container
running locally, there's no need to get anything connected to
kernelci.org with your local setup.


>> 2. Is the following understanding of kci_test's options correct​?
>> For example:
>> ./kci_test generate
>>
>>   --bmeta-json=linux/_install_/bmeta.json \      //bmeta file in build directory generated by kci_build
>>   --dtbs-json=linux/_install_/dtbs.json \             //dtbs file in build directory generated by kci_build​
>>   --plan=baseline_qemu \                                      // test_plan
>>   --target=qemu_arm64-virt-gicv3 \                     //device_type
>>   --lab=lab-name \                                                   //lab name which is recorded in lab-configs.yaml 
>>  --user=kernelci-user-name \                               //user of lava for kernelci test
>>   --token=abcd-7890 \                                            //token of lava user for kenelci test
>>   --lab-json=lab-name.json \                                  //JSON file generated by executing command get_lab_info
>>   > job.yaml
>>
> 
> With all users/token and labname created in 1), it will works (generated some jobs in a directory "$labname"
> 
>> 3. Error is occurred when executing the following command. Is there any problem with parameter specification?
>> Command line : $. / KCI_ test get_ lab_ info --lab=lab-linaro-lkft --lab-json=lab-linaro- lkft.json
>> Error message:   $ attributeerror: 'nonetype' object has no attribute 'scheduler'
>>

You're trying to use Linaro's LKFT lab, which kernelci.org, and
you don't have tokens for that which is normal.  In your case,
with your local setup, you need to use your own LAVA instance
with your local KernelCI Docker container.

To do that, you need to add an entry in lab-configs.yaml, for
example:

  local-lab:
    lab_type: lava
    url: 'http://localhost/RPC2'


The `local-lab` name is arbitrary but you'll need to use it in
the kci_test command line.  The URL needs to match your local
LAVA lab running in your Docker container.

Once you have this, you need to produce a kernel build using
kci_build, as explained in the kernelci-docs.  You can then
generate some tests for it using kci_test as also explained in
the docs, except you'll be using --lab=local-lab and your owh API
token.


What I've explained here, about how to set up a lab, seems like a
gap in the documentation so we should try to improve it for other
users in your case.

Best wishes,
Guillaume

Re: How to use kci_test?

[leimaohui]

Hi, Guillaume, LABBE

I have solved this issue with your replies. Thank both of you very much!

Best regards
Lei


________________________________________
From: kernelci@groups.io <kernelci@groups.io> on behalf of Guillaume Tucker <guillaume.tucker@collabora.com>
Sent: Monday, 29 June 2020 16:04
To: Lei, Maohui
Cc: kernelci@groups.io; clabbe@baylibre.com
Subject: Re: How to use kci_test?

On 28/06/2020 07:38, Corentin Labbe wrote:
> On Mon, Jun 22, 2020 at 03:10:31AM +0000, leimaohui wrote:
>> Hi, all
>>
>> I am learning to use kernelci. At present, I have installed kernelci docker and lava docker, and use kci_ build builds the kernel.
>> Using kci_test, we encountered some problems:
>>
>> 1. What do I need to do to connect kernelci and lava before the test command?
>>
>
> Hello
>
> You need to create a lab in kernelci, you can use https://github.com/kernelci/kernelci-admin for this
> With this lab created, you will have a token for it.
>
> For LAVA, you need to have a LAVA instance working with a qemu passing healthcheck.
> Then you need to create an user and get the token of it.

As you've installed LAVA Docker, you should have a local LAVA
lab.  You need to create an API token for it with a user
called "kernel-ci".  Then as you have a KernelCI Docker container
running locally, there's no need to get anything connected to
kernelci.org with your local setup.


>> 2. Is the following understanding of kci_test's options correct​?
>> For example:
>> ./kci_test generate
>>
>>   --bmeta-json=linux/_install_/bmeta.json \      //bmeta file in build directory generated by kci_build
>>   --dtbs-json=linux/_install_/dtbs.json \             //dtbs file in build directory generated by kci_build​
>>   --plan=baseline_qemu \                                      // test_plan
>>   --target=qemu_arm64-virt-gicv3 \                     //device_type
>>   --lab=lab-name \                                                   //lab name which is recorded in lab-configs.yaml
>>  --user=kernelci-user-name \                               //user of lava for kernelci test
>>   --token=abcd-7890 \                                            //token of lava user for kenelci test
>>   --lab-json=lab-name.json \                                  //JSON file generated by executing command get_lab_info
>>   > job.yaml
>>
>
> With all users/token and labname created in 1), it will works (generated some jobs in a directory "$labname"
>
>> 3. Error is occurred when executing the following command. Is there any problem with parameter specification?
>> Command line : $. / KCI_ test get_ lab_ info --lab=lab-linaro-lkft --lab-json=lab-linaro- lkft.json
>> Error message:   $ attributeerror: 'nonetype' object has no attribute 'scheduler'
>>

You're trying to use Linaro's LKFT lab, which kernelci.org, and
you don't have tokens for that which is normal.  In your case,
with your local setup, you need to use your own LAVA instance
with your local KernelCI Docker container.

To do that, you need to add an entry in lab-configs.yaml, for
example:

  local-lab:
    lab_type: lava
    url: 'http://localhost/RPC2'


The `local-lab` name is arbitrary but you'll need to use it in
the kci_test command line.  The URL needs to match your local
LAVA lab running in your Docker container.

Once you have this, you need to produce a kernel build using
kci_build, as explained in the kernelci-docs.  You can then
generate some tests for it using kci_test as also explained in
the docs, except you'll be using --lab=local-lab and your owh API
token.


What I've explained here, about how to set up a lab, seems like a
gap in the documentation so we should try to improve it for other
users in your case.

Best wishes,
Guillaume