lava-users

lava-users@lists.lavasoftware.org

1 participants
912 discussions

About the cursor movement in the device config file.

by Elaine Wu (wuyanjun)

hi, all, I am using the new uefi, it use the cursor movement and the Enter to enter the entry. So I use the config file to write it, but I found it can not work well. the config is below. boot_cmds_ramdisk_sata = expect "Move Highlight", sendline "\033[B", sendline "\033[B", sendcontrol "M", sendline "\033[B", sendline "\033[B", sendline "\033[B", sendline "\033[B", sendline "\033[B", sendline "\033[B", sendcontrol "M", expect "D02", sendline "provision {SERVER_IP} -u htsat -p hello8943217 -f Image_D02 -a 10000", expect "succ" , sendline "norwfmem 100000 100000 1f00000", expect "OK", sendline "provision {SERVER_IP} -u htsat -p hello8943217 -f hip05-d02.dtb -a 100000", expect "succ", sendline "spiwfmem 100000 300000 100000", expect "OK", expect "OK", sendline "exit", expect "Select Language", sendline "\033[B", sendline "\033[B", sendcontrol "M", sendline "\033[B", sendline "\033[B", sendline "\033[B", sendline "\033[B", sendcontrol "M" After I read the source code of LAVA. I found it use the pexpect.spawn to interact with the terminal, So I directly writte a python file to directly use spawn to interact with the terminal, and it can work well . The source code is below. import sys from pexpect import spawn child = spawn("board_connect 2") # this is similar with minicom logfile = "/tmp/test_for_terminal.log" fd = open(logfile, 'a+') child.logfile = fd child.expect("to stop automatical booting", timeout=120) child.sendline("b") child.expect("Move Highlight") ## boot from sata child.sendline("\033[B") child.sendline("\033[B") child.sendcontrol("M") child.sendline("\033[B") child.sendline("\033[B") child.sendline("\033[B") child.sendline("\033[B") child.sendline("\033[B") child.sendline("\033[B") child.sendcontrol("M") child.expect("D02") child.sendline("provision 192.168.6.100 -u htsat -p hello8943217 -f Image_D02 -a 10000") child.expect("succ") child.sendline("norwfmem 100000 100000 1f00000") child.expect("OK") child.sendline("provision 192.168.6.100 -u htsat -p hello8943217 -f hip05-d02.dtb -a 100000") child.expect("succ") child.sendline("spiwfmem 100000 300000 100000") child.expect("OK") child.expect("OK") #child.interact() child.sendline("exit") child.expect("Select Language") child.sendline("\033[B") child.sendline("\033[B") child.sendcontrol("M") child.sendline("\033[B") child.sendline("\033[B") child.sendline("\033[B") child.sendline("\033[B") child.sendcontrol("M") child.interact() So I don't know why in LAVA it can not work. Also I have realized a function named /sendcursor /similar with the sendcontrol in the lava_dispatcher package especially in the /usr/lib/python2.7/dist-package/lava_dispatcher/utils.py, and it call the pexpect.spawn.sendline to send contents to the child process. But it still have the same phenomenon with using sendline(namely won't select the entry in the uefi menu). Does this problem is caused by the dashboard showing? The attached files are the log files when I use the python file to execute the interaction and the one when LAVA execute it. Thanks for your help. Elaine Hisilicon turing software and architecture

8 years, 8 months

Configuration file for new devices

by Quentin Schulz

Hi, 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 some from: https://github.com/Linaro/lava-dispatcher/tree/release/lava_dispatcher/defa… 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 Regards, Quentin

8 years, 8 months

[PATCH] device-types: add meson8b-odroidc1.conf default

by Marc Titinger

From: Marc Titinger <mtitinger(a)baylibre.com> - specific u-boot prompt - specific C-c interrupt char - uImage only: hardkernel u-boot sources are heavily hardcoded in an old u-boot version (no bootz) Signed-off-by: Marc Titinger <mtitinger(a)baylibre.com> --- .../device-types/meson8b-odroidc1.conf | 44 ++++++++++++++++++++++ 1 file changed, 44 insertions(+) create mode 100644 lava_dispatcher/default-config/lava-dispatcher/device-types/meson8b-odroidc1.conf diff --git a/lava_dispatcher/default-config/lava-dispatcher/device-types/meson8b-odroidc1.conf b/lava_dispatcher/default-config/lava-dispatcher/device-types/meson8b-odroidc1.conf new file mode 100644 index 0000000..96232b4 --- /dev/null +++ b/lava_dispatcher/default-config/lava-dispatcher/device-types/meson8b-odroidc1.conf @@ -0,0 +1,44 @@ +client_type = bootloader +send_char = False +uimage_only = True +append_dtb = True + +u_load_addrs = + 0x20000000 + 0x22000000 + 0x21000000 + +z_load_addrs = + 0x20000000 + 0x22000000 + 0x21000000 + +boot_cmds_ramdisk = + setenv autoload no, + setenv kernel_addr_r "'{KERNEL_ADDR}'", + setenv initrd_addr_r "'{RAMDISK_ADDR}'", + setenv loadkernel "'tftp ${kernel_addr_r} {KERNEL}'", + setenv loadinitrd "'tftp ${initrd_addr_r} {RAMDISK}; setenv initrd_size ${filesize}'", + setenv bootargs "'console=ttyAML0,115200n8 root=/dev/ram0 ip=dhcp'", + setenv bootcmd "'dhcp; dhcp; setenv serverip {SERVER_IP}; run loadkernel; run loadinitrd; {BOOTX}'", + run bootcmd + +boot_cmds_nfs = + setenv autoload no, + setenv kernel_addr_r "'{KERNEL_ADDR}'", + setenv initrd_addr_r "'{RAMDISK_ADDR}'", + setenv loadkernel "'tftp ${kernel_addr_r} {KERNEL}'", + setenv loadinitrd "'tftp ${initrd_addr_r} {RAMDISK}; setenv initrd_size ${filesize}'", + setenv nfsargs "'setenv bootargs console=ttyAML0,115200n8 root=/dev/nfs rw nfsroot={SERVER_IP}:{NFSROOTFS},tcp,hard,intr ip=dhcp'", + setenv bootcmd "'dhcp; setenv serverip {SERVER_IP}; run loadkernel; run loadinitrd; run nfsargs; {BOOTX}'", + run bootcmd + +bootloader_prompt = odroidc# +interrupt_boot_prompt = key to stop autoboot +interrupt_boot_control_character = c + +boot_options = + boot_cmds + +[boot_cmds] +default = boot_cmds -- 2.5.0

8 years, 8 months

lava job strucked when execute the config file.

by Wu Yanjun (Elaine)

hi, I have two questions to ask: 1. 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. then The log file of the lava job, the log of boot manually and the config file has been attached. 2. 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. -- Best Wishes wuyanjun (Elaine) Hisilicon Turing Software and Architecture

8 years, 9 months

the board uefi use dialog to boot, how can I configuare the lava device-type config file.

by Elaine Wu (wuyanjun)

hi, all, 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. and Thank you very much. Elaine (wuyanjun) Hisilicon, Turing Architecture and Software

8 years, 9 months

adding per-action comment or brief description or meta-data into the bundle

by Marc Titinger

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. { "command": "lava_command_run", "metadata": { "comment": "comment1" }, "parameters": { "commands": [ "uname -a" ] } }, { "command": "lava_command_run", "metadata": { "comment": "comment2" }, "parameters": { "commands": [ "ls -al" ] } }, The result bundle will contain the same metadata for each lava-command: "attributes": { "comment": "comment2", <=== same value "image.type": "kernel-ci", .... snip ... "logging_level": "DEBUG", "device.tree": "omap4-panda-es.dtb" }, "test_id": "lava-command" IOW, how do I assign a brief description to an action ? Thanks and regards, Marc.

8 years, 9 months

Reviews

by Neil Williams

https://review.linaro.org/#/c/10593/ and https://review.linaro.org/#/c/10595/ have some comments which need to be addressed. The simplest way is to register for a Linaro Community account and then you can login to gerrit yourself. Alternatively, the comments can be addressed by email and the reviews updated. https://ci.linaro.org/job/lava-dispatcher/836/console -- Neil Williams ============= neil.williams(a)linaro.org http://www.linux.codehelp.co.uk/

8 years, 9 months

回复： Forward of moderated message

by wangbo

Hi Neil, 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. # test_script.yaml run: steps: - echo "hello world" - ./android/script/script.py # run.sh in DUT ###default parameters from yaml### ###### ###test parameters from json### ###### ###other parameters### LAVA_SERVER_IP='172.16.117.50' TARGET_TYPE='android' ###### set -e export TESTRUN_ID=python cd /data/local/tmp/lava-mstar01/tests/0_c7a6f9e0-ae70-4d8b-8c06-f6da04b7a26c UUID=`cat uuid` echo "<LAVA_SIGNAL_STARTRUN $TESTRUN_ID $UUID>" #wait for an ack from the dispatcher read echo "hello world" ./android/script/script.py echo "<LAVA_SIGNAL_ENDRUN $TESTRUN_ID $UUID>" #wait for an ack from the dispatcher read ------------------ 原始邮件 ------------------ 发件人: "Neil Williams";<neil.williams(a)linaro.org>; 发送时间: 2016年1月30日(星期六) 晚上11:29 收件人: "wangbo"<wangbo.hfut(a)qq.com>; 抄送: "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 tests do. > 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. > > https://lists.linaro.org/pipermail/lava-announce/2015-November/000003.html > > 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. > > https://staging.validation.linaro.org/static/docs/installing_on_debian.html… > > 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 > moment. > >> 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 > ============= > neil.williams(a)linaro.org > http://www.linux.codehelp.co.uk/ -- Neil Williams ============= neil.williams(a)linaro.org http://www.linux.codehelp.co.uk/

8 years, 9 months

Missing apache config file

by Felsch Marco

Dear LAVA-Team, 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: https://validation.linaro.org/static/docs/installing_on_debian.html#install… 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 ******************************************************************* mailto:marco.felsch@tq-group.com TQ-Systems GmbH 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 http://www.tq-group.com<http://www.tq-group.com/> 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

8 years, 9 months

For all lava-tool users

by Neil Williams

If you are running lava-tool on Debian unstable (sid) or testing (stretch), the new version of python-keyring (8.4.1-1) will break lava-tool at versions lower than 0.14-2 as it has moved a previously supported component into a separate package which did not previously exist. Sadly, the lava-tool maintainers were not made aware of this change in functionality in advance - lava-tool simply stopped working in unstable. lava-tool 0.14-2 has been uploaded with the only change being a dependency on python-keyrings.alt which is the new package which provides the functionality formerly available as part of python-keyring itself. python-keyrings.alt already exists in Debian testing and can be safely installed ahead of the upgrade of python-keyring, so users may wish to install python-keyrings.alt now in order to maintain functionality. Version 8.4 of python-keyring will migrate into Debian testing before version 0.14-2 of lava-tool can migrate, so users of testing may have a short window where lava-tool fails in Debian testing if python-keyrings.alt is not installed in advance. Ubuntu users may also be affected as python-keyring is a "main" package, so may possibly update in Xenial Xerus - however as lava-tool is a "universe" package, it may not be possible to upgrade Xenial to 0.14-2 of lava-tool. Users are advised to manually install python-keyrings.alt to maintain functionality. lava-tool users running Jessie are not affected (but are advised to upgrade to 0.14-1~bpo8+1 from jessie-backports for other updates, new functionality and bug fixes). -- Neil Williams ============= neil.williams(a)linaro.org http://www.linux.codehelp.co.uk/

8 years, 9 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

lava-users