We are building a LAVA lab which will be soon integrated to KernelCI. We
want to add most of our boards to LAVA that's why we created
configuration files for the old dispatcher (the one used by KernelCI at
this moment) for all device types we own.
I would like to know if you were interested in getting those
configuration files to put them in your git repository (we are using
If yes, what is your naming convention? I've seen sama53d for the
SAMA5D3 Xplained for example.
This is the list of boards currently added to our lab:
Board name Current configuration file's name
NextThingCo. CHIP sun5i-r8-chip
Boundary Devices Nitrogen6x imx6q-nitrogen6x
ATMEL at91rm9200ek at91rm9200ek
ATMEL at91sam9261ek at91sam9261ek
ATMEL at91sam9m10g45ek at91sam9m10g45ek
ATMEL at91sam9x25ek at91sam9x25ek
ATMEL at91sam9x35ek at91sam9x35ek
ATMEL sama5d31ek sama5d31ek
ATMEL sama5d36ek sama5d36ek
ATMEL sama5d44ek sama5d4ek
Marvell Armada 385 AP armada-385-db-ap
Solidrun Clearfog armada-388-clearfog
Plathome OpenBlocks AX3 armada-xp-openblocks-ax3-4
I have two questions to ask:
I am using the lava to boot the D02 board, it can successfully execute
before. But it failed after I update the uefi and rewrite the config
file. But when I execute the config file manually, it succeed booting
the board. And I can figure out what is wrong. The version of LAVA I
used is 2015.9.post1, and I use LAVA v1.
From the figure, we can see it is strucked when booting the kernel.
The log file of the lava job, the log of boot manually and the config
file has been attached.
The uefi is used need to control by cursor movement, so I need to send
KEY-DOWN in the d02.conf file. But when I use 'sendline "\033[A"' or
‘sendline "\16[A"', I found it can not work in the LAVA. So I want to
know if we have any method to realize it?
Thank you very much.
Hisilicon Turing Software and Architecture
The uefi the board used has upgraded, so that the configuration of it
can not be used in the current environment. Because now the uefi use the
dialog to show the menu.
As I know, the expect and sendline in the lava XXX.conf can not work
well in this situation. Does you know how to config the XXX.conf to
support this kind of uefi?
The menu of the uefi is below.
Thank you very much.
Hisilicon, Turing Architecture and Software
Hi Neil and all,
how do I add per-action comments or meta data so that I can parse them
from the result bundle:
the following for instance will pass the schema validation, but the
result bundle will degenerate into keeping only the last "comment"
metadata entry, while I'd like a per-action metadata entry.
The result bundle will contain the same metadata for each lava-command:
"comment": "comment2", <=== same value
.... snip ...
IOW, how do I assign a brief description to an action ?
Thanks and regards,
But the problem is I want to define a job and use python script to communicate with the Android DUT, for example I want to use script.py in dispatcher to control the DUT. And the "lava_test_shell" will copy all these commands in steps to run.sh.
- echo "hello world"
# run.sh in DUT
###default parameters from yaml###
###test parameters from json###
echo "<LAVA_SIGNAL_STARTRUN $TESTRUN_ID $UUID>"
#wait for an ack from the dispatcher
echo "hello world"
echo "<LAVA_SIGNAL_ENDRUN $TESTRUN_ID $UUID>"
#wait for an ack from the dispatcher
------------------ 原始邮件 ------------------
发件人: "Neil Williams";<neil.williams(a)linaro.org>;
发送时间: 2016年1月30日(星期六) 晚上11:29
抄送: "Lava Users Mailman list"<lava-users(a)lists.linaro.org>;
主题: Re: Forward of moderated message
On 29 January 2016 at 04:08, wangbo <wangbo.hfut(a)qq.com> wrote:
> Hi Neil,
> Thanks very much to your quickly and warmly answer.
> One more question:
> LAVA copy all the test scripts defined in the YAML to the DUT at the
> specified directory, then the job will be executed on the DUT.
The LAVA test shell scripts are POSIX shell. If a shell is not
available, the test can be rewritten to use ADB commands, as the CTS
> And if I want
> to test one android device, but almost all the android images don't support
> python interpreter,
LAVA does not run any python code on the DUT unless the test writer
puts python commands into their test shell definition YAML. The python
code only runs on the dispatcher and handles communications over the
serial port (or using ADB).
> so it's impossible to write case with python, in most
> cases we should use shell to run the test case. But sometimes we want to use
> Appium/Robotium to test the android image, and use LAVA to deploy the image,
> analyze and record the test results, so LAVA is unavailable in such
> conditions. Do you have any advice to integrate these tools in LAVA or will
> LAVA support such conditions in the future.
You'd need to use multinode (as with CTS) to install the test support
binaries into a VM which then communicates with the device. That VM
then reports results that are retrieved with LAVA.
> Best Regards.
> ------------------ 原始邮件 ------------------
> 发件人: "Neil Williams";<neil.williams(a)linaro.org>;
> 发送时间: 2016年1月29日(星期五) 凌晨3:27
> 收件人: "wangbo"<wangbo.hfut(a)qq.com>;
> 抄送: "Lava Users Mailman list"<lava-users(a)lists.linaro.org>;
> 主题: Re: Forward of moderated message
>> From: wangbo <wangbo.hfut(a)qq.com>
>> Date: Thu, 28 Jan 2016 20:39:25 +0800
>> Subject: LAVA uninstall and upgrade, build method from the source code
>> Hi all,
>> I installed LAVA on Ubuntu 14.04 in our lab, but later we plan to upgrade
>> the system to Ubuntu 15.10, so what should I do now?
> I'm afraid the only long term option is to migrate to Debian Jessie,
> possibly using a VM, and then using jessie-backports. It is uncertain
> whether it will be possible to support LAVA on the upcoming Ubuntu
> Xenial 16.04LTS and support for Trusty has already been frozen. There
> have been problems upgrading from 14.04 - these issues have already
> been discussed on the lists.
> The next upload of LAVA should be able to migrate into Ubuntu ahead of
> the cut off for the Xenial release but that is outside our control. It
> is also unknown whether it will be possible to maintain a system based
> on Xenial - the LAVA software team will be unable to maintain such
> support and users would need to be proactive in fixing problems that
> may arise.
>> Because I have already installed LAVA, so should I uninstall it firstly,
>> and then use apt-get install to reinstall LAVA? But I can't find more
>> information about this in the website, can you give me some advice, thanks
>> very much.
> The main problems will be with the database, so building in any way
> will have the same difficulties. Trusty is, sadly, a dead end at the
>> And, how to install LAVA from the source code?
> Not supported - installation is only supported as Debian packages.
> LAVA is much more than a pip install / virtualenv can ever manage.
>> LAVA includes different parts, like lava-server, lava-dispatcher,
>> lava-tool, etc. So which one should be installed firstly? By the way in the
>> Git, for example "https://git.linaro.org/lava/lava-server.git/tree", there
>> is no document about the install method. Now, I will modify some code to
>> meet our demands in our lab, and then replace the corresponding file. We
>> plan to manage the code with Git too. So if we know the install method from
>> the source code, it will be better to build the code.
> There is no documentation for installing from git because the
> installation method has moved to using packages. We abandoned the old
> install from git methods a long time ago due to interminable bugs and
> insolvable dilemmas.
> During the migration to the new dispatcher, things are too complex to
> support more than Debian Jessie (and the next Debian release,
> Stretch). Once the migration is complete (in 2017), the advantages of
> the new design should also make it easier to support other operating
> systems. We are a long way from that at the moment.
> Neil Williams
I have set up two new LAVA instances (master, worker) based on the production release 2016.02.
The installation worked fine but I can't switch the apache site.
I followed the instructions on:
Then I searched for the lava-server.conf file on my system, but didn't find it.
It looks like it isn't installed.
I also tried to add it to add it manually, but it didn't worked.
i.A. Marco Felsch
Entwicklung Standort Chemnitz
******************** Wir sind umgezogen! ********************
Tel. +49 371 433151-34, Fax +49 371 433151-22
Zwickauer Strasse 173, 09116 Chemnitz
Mühlstraße 2, 82229 Seefeld
Amtsgericht München, HRB-Nr. 105 018, UST-IdNr. DE 252 251 764
WEEE-Reg.-Nr. DE 46311528
Sitz der Gesellschaft: Seefeld
Geschäftsführer: Dipl.-Ing. (FH) Detlef Schneider, Dipl.-Ing. (FH) Rüdiger Stahl
Besuchen Sie uns / Visit us:
light + building, Frankfurt am Main, March 13 - 18, 2016, Hall 9.0, Stand C80
Aircraft Interiors Expo, Hamburg, April 5 - 7, 2016, Stand 2A20
Automatica, Munich, June 21 - 24, 2016
Intersolar, Munich, June 22 - 24, 2016