Lava-users August 2018

lava-users@lists.linaro.org

22 participants
32 discussions

In which config file is described the path of uboot and kernel image or qemu?

by ljh_dev

Through web admin interface,I had added qemu device,and web devices list can display qemu device. It seems qemu device had startuped ok. We know that if linux device startup successfully it must included uboot and kernel image. But where are the uboot image and kernel image of qemu ? In which config file is described the path of uboot and kernel image?

5 years, 10 months

about qemu device dictionary config

by ljh_dev

I am building lava test system and currently add new addvice. According to document than step of "Adding a dictionary to the first QEMU device",follow config items neet to write to .jianja2 file. {% extends 'qemu.jinja2' %} {% set mac_addr = '52:54:00:12:34:59' %} {% set memory = '1024' %} Which file is to be writen to above config items ?does its directory path must be at path:/etc/lava-server/dispatcher-config/device-types/? How to make these items take effect immediatly?which command to use to take effect above config items? the document is not said.

5 years, 10 months

booting from USB thumb drive

by Hussin, Mohamad Noor Alim

Hi, I using LAVA version 2018.5-post1 to boot from USB thumb drive using Yocto Project's image. The LAVA job definition contain 2 deployments and booting actions. The first deployment is deploy the image to NFS server and boot using TFTP method. The second deployment is download an image to DUT and flash it on USB thumb drive. The DUT was able to download the image however it failed at flash to thumb drive. I'm use dd command as my tool to flash the image. Below is an example on lava-job definition and output message from LAVA. Due to this issue, I unable to boot from USB thumb drive. Did anyone know what is the problem? Snipped code from lava-job definition to deploy on USB thumb drive - deploy: timeout: minutes: 30 to: usb image: url: file:///home/user/image/yocto-image.xz compression: xz root_partition: 1 device: 'boot' download: tool: '/usr/bin/wget' prompt: 'HTTP request sent, awaiting response...' options: '--S {DOWNLOAD_URL}' os: oe The command from LAVA wget http://lavadisptcher.com/tmp/storage/image/yocto-image.xz | dd of=/dev/disk/by-id/<myusbthumdriveid> bs=4M This is the output message form LAVA after download flash the image 0+0 records in 0+0 records out 0 bytes copied Regards, Alim Hussin

5 years, 10 months

when add a new real device, do the uboot and kernel program need to be modified according to the lava specifications?

by ljh_dev

Hi, I think the lava web document is relatively simple.I still have some basic questions that didn’t understand. I want to add new real board(for example the arm development board,includes serial,ethernet interface etc)into lava environment. The board had ordinary uboot program, and uboot can download linux kernel image by ethernet interface. If treat it as DUT to run test,do the uboot and kernel program need to be modified or both configuration need to be modified?

5 years, 10 months

is the uboot image location specified in the job definition file?

by ljh_dev

When used real board(not qemu),is the uboot image location specified in the job definition file? If so, what keyword is used to indicate the uboot image location? The lava document description is not enough.

5 years, 10 months

How to rename a devicetype (and deprecate the old one)

by LABBE Corentin

Hello I have a cubietruck in LAVA, but its devicetype does not follow the rule "devicetype should be the same as devicetree name". Diverting from this rule, make difficult to find if the device is already handled by LAVA. I have lots of other boards which suffer the same problem (odroid-xu3 for example) Do you already have a process for renaming devicetype ? If not, why about duplicating to the correct name (sun7i-a20-cubietruck) and adding some tags (comment like "{# set deprecated = true}") to the old one. The deprectation warning could be printed by the LAVA web interface like the warning about not having health checks. After some release, the deprecated devicetype could be removed. Regards

5 years, 10 months

Does board test system must include PDU device?

by john zhang

Does board test system must include PDU device? If test system has no PDU and in job definition the boot action method is u-boot. When board had startup to enter linux interactive environment and submit job at this time. Then how does dispatcher restart the board?

5 years, 10 months

How to restart LAVA server master service after LAVA server host restart

by Yuan, ZhanghuiX

Hi LAVA team, I meet one critical error. We restart our LAVA server host machine. We can’t know how to restart our LAVA server service. Could you tell me how to restart LAVA server master service with detail steps? Thanks! The LAVA server is not installed by us. So we are not clear about this. BR/Zhanghui

5 years, 10 months

How the parameter {KERNEL} of boot action be passed ?

by ljh_dev

https://validation.linaro.org/static/docs/v2/actions-boot.html#index-9 - setenv loadkernel 'tftp {KERNEL_ADDR} {KERNEL}' It say the {KERNEL} will be substituted. Where is {KERNEL} variable defined? When I submit job definition by web interface,I did't find where to define {KERNEL} variable

5 years, 10 months

transfer_overlay file in the same location regardless of test

by Jorgen Peddersen

Hi, I'm trying to use a situation where a large bulk of similar jobs are being sent to several devices of the same device type. These devices require the 'transfer_overlay' option in order for the tests to work due to their setup. We currently are using a single master and worker on the same server. It seems that the same transfer overlay file location (i.e., /var/lib/lava/dispatcher/tmp/overlay-1.3.2.5.tar.gz) is used regardless of the job id and that some of our jobs are experiencing a collision trying to use different copies of that file at the same time. Thus, one of our jobs is deleting the transfer overlay file before another job tries to delete it and the second gets errors. This is the error LAVA produces when viewing the job in the GUI: File "/usr/bin/lava", line 11, in <module> load_entry_point('lava-tool==0.25', 'console_scripts', 'lava')() File "/usr/lib/python2.7/dist-packages/lava/tool/dispatcher.py", line 150, in run raise SystemExit(cls().dispatch(args)) File "/usr/lib/python2.7/dist-packages/lava/tool/dispatcher.py", line 140, in dispatch return command.invoke() File "/usr/lib/python2.7/dist-packages/lava/dispatcher/commands.py", line 247, in invoke self.args.validate) File "/usr/lib/python2.7/dist-packages/lava/dispatcher/commands.py", line 91, in run_pipeline_job exitcode = job.run() File "/usr/lib/python2.7/dist-packages/lava_dispatcher/pipeline/job.py", line 340, in run self.cleanup(self.connection) File "/usr/lib/python2.7/dist-packages/lava_dispatcher/pipeline/job.py", line 375, in cleanup self.pipeline.cleanup(connection) File "/usr/lib/python2.7/dist-packages/lava_dispatcher/pipeline/action.py", line 251, in cleanup child.cleanup(connection) File "/usr/lib/python2.7/dist-packages/lava_dispatcher/pipeline/action.py", line 649, in cleanup self.internal_pipeline.cleanup(connection) File "/usr/lib/python2.7/dist-packages/lava_dispatcher/pipeline/action.py", line 251, in cleanup child.cleanup(connection) File "/usr/lib/python2.7/dist-packages/lava_dispatcher/pipeline/action.py", line 649, in cleanup self.internal_pipeline.cleanup(connection) File "/usr/lib/python2.7/dist-packages/lava_dispatcher/pipeline/action.py", line 251, in cleanup child.cleanup(connection) File "/usr/lib/python2.7/dist-packages/lava_dispatcher/pipeline/actions/boot/__init__.py", line 458, in cleanup os.unlink(self.url) OSError: [Errno 2] No such file or directory: '/var/lib/lava/dispatcher/tmp/overlay-1.3.2.5.tar.gz' We are working on the 2017.7 build of LAVA, so if this has been changed in a later build, please let me know. If this has not been updated, is there another way to change things so that each job uses a different name and/or location for the overlay file? Thanks, Jorgen Peddersen Jorgen Peddersen Researcher t +61 2 6103 4700 m e jorgen.peddersen(a)seeingmachines.com a 80 Mildura Street, Fyshwick ACT 2609, Australia SEEINGMACHINES.COM<http://seeingmachines.com> [SEEINGMACHINES] This email may contain confidential information. If you are not the intended recipient, destroy all copies and do not disclose or use the information within. Any content that is not concerned with the business of the Seeing Machines Group reflects the views of the sender only, not those of Seeing Machines. No warranties are given that this email does not contain viruses or harmful code. [http://www.seeingmachines.com/wp-content/uploads/2018/04/sm-email-twitter-i…] <https://twitter.com/seeingmachines> [http://www.seeingmachines.com/wp-content/uploads/2018/04/sm-email-linkedin-…] <https://www.linkedin.com/company/258949/>

5 years, 10 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Lava-users August 2018