From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Sun, 28 Jun 2020 08:38:34 +0200 From: "Corentin Labbe" Subject: Re: How to use kci_test? Message-ID: <20200628063834.GA3784@Red> References: MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: 8bit List-ID: To: kernelci@groups.io, leimaohui@cn.fujitsu.com 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