All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Corentin Labbe" <clabbe@baylibre.com>
To: kernelci@groups.io, leimaohui@cn.fujitsu.com
Subject: Re: How to use kci_test?
Date: Sun, 28 Jun 2020 08:38:34 +0200	[thread overview]
Message-ID: <20200628063834.GA3784@Red> (raw)
In-Reply-To: <bc20a3ed96fd4cedbad73e21f826a9ef@G08CNEXMBPEKD05.g08.fujitsu.local>

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

  reply	other threads:[~2020-06-28  6:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-22  3:10 How to use kci_test? leimaohui
2020-06-28  6:38 ` Corentin Labbe [this message]
2020-06-29  8:04   ` Guillaume Tucker
2020-06-30  7:18     ` leimaohui
     [not found] <161ABF04116C5EFF.11535@groups.io>
2020-06-28  3:55 ` leimaohui

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200628063834.GA3784@Red \
    --to=clabbe@baylibre.com \
    --cc=kernelci@groups.io \
    --cc=leimaohui@cn.fujitsu.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.