Hello Remi,
A while back you gave a presentation [0] on your efforts on a new tool called LAVAPeur.
The project looks like a great idea.
I was just wondering, what is the current status of this work?
[0] https://resources.linaro.org/en/resource/hj6KGw9fnhKVgvXDdE3qAS
Kind regards, Chris
Hi,
I'm facing an issue after updating the base-uboot file on the server.
*Configuration Error: missing or invalid template.*
*Jobs requesting this device type will not be able to start until a
template is available on the master.*
I have restarted the server and dispatcher but no update. All the devices
went offline automatically.
Any advice to resolve this issue would be appreciated.
Thank you
Hi Team,
Good day to you!
I'm making a dispatcher setup to connect new devices and run tests. In
order to do this, I have connected all the required hardware correctly and
created configuration files by following Lava documentation. I Am able to
control the device with the relay board automatically and can login using
telnet.
I'm trying to run my initial test job definition, It downloads the image
but fails to flash the image on device with the below message:
- {"dt": "2022-08-22T09:07:45.799863", "lvl": "debug", "msg": "Calling:
'nice' 'flash' 'pk_raspi-unit1' '{package}'"}
- {"dt": "2022-08-22T09:07:45.809654", "lvl": "debug", "msg": ">>
/var/lib/lava/dispatcher/tmp/466/deploy-flasher-p2k8tvri
/var/lib/lava/dispatcher/tmp/466/deploy-flasher-p2k8tvri\r"}
- {"dt": "2022-08-22T09:07:45.811510", "lvl": "debug", "msg": ">> \r"}
- {"dt": "2022-08-22T09:07:45.811674", "lvl": "debug", "msg": ">> 7-Zip
[64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21\r"}
- {"dt": "2022-08-22T09:07:45.811955", "lvl": "debug", "msg": ">> p7zip
Version 16.02 (locale=C.UTF-8,Utf16=on,HugeFiles=on,64 bits,8 CPUs Intel(R)
Core(TM) i5-8265U CPU @ 1.60GHz (806EB),ASM,AES-NI)\r"}
- {"dt": "2022-08-22T09:07:45.812045", "lvl": "debug", "msg": ">> \r"}
- {"dt": "2022-08-22T09:07:45.812121", "lvl": "debug", "msg": ">> Scanning
the drive for archives:\r"}
- {"dt": "2022-08-22T09:07:45.812195", "lvl": "debug", "msg": ">> 0M
Scan\b\b\b\b\b\b\b\b\b \b\b\b\b\b\b\b\b\b\r"}
- {"dt": "2022-08-22T09:07:45.812266", "lvl": "debug", "msg": ">> ERROR: No
more files\r"}
- {"dt": "2022-08-22T09:07:45.812366", "lvl": "debug", "msg": ">>
{package}\r"}
- {"dt": "2022-08-22T09:07:45.812434", "lvl": "debug", "msg": ">> \r"}
- {"dt": "2022-08-22T09:07:45.812712", "lvl": "debug", "msg": ">> \r"}
- {"dt": "2022-08-22T09:07:45.812790", "lvl": "debug", "msg": ">> \r"}
- {"dt": "2022-08-22T09:07:45.812860", "lvl": "debug", "msg": ">> System
ERROR:\r"}
- {"dt": "2022-08-22T09:07:45.812929", "lvl": "debug", "msg": ">> Unknown
error -2147024872\r"}
- {"dt": "2022-08-22T09:07:45.813221", "lvl": "debug", "msg": "Returned 2
in 0 seconds"}
- {"dt": "2022-08-22T09:07:45.813306", "lvl": "error", "msg": "Unable to
run 'nice' '['flash', 'pk_raspi-unit1', '{package}']'"}
- {"dt": "2022-08-22T09:07:45.813411", "lvl": "exception", "msg": "Unable
to flash the device"}
Any suggestion to overcome the issue would be very helpful.
Attached log file
Best Regards.
Hello Team,
I'm a new bee to the LAVA environment and learning to perform the
automation testing on my DUT.
But my problem is I have my document which performs booting using serial
and run tests. I need your help here to write a definition that calls
script located in dispatcher and timeout till completion of tests in
script. No need to deploy and boot
I have tried writing only 'test' in actions but it is not successful.
Please suggest the best way to approach to execute script from dispatcher.
Thanks in advance.
Hello, I am a user of the lava software package.
For one of the use cases, I need an ipxe bootloader, I tried to use the one
you collected from here https://docs.lavasoftware.org/lava/ipxe.html, but
it does not have download via nfs.
I tried to build a regular ipxe loader, but it is not compatible with lava
due to text colorization. Can you please tell me if it is possible to find
somewhere a patch that was used in the build of the bootloader to remove
the text colorization?
Best regards,
Volga Bogoslovskiy
Hello,
We are writing an interactive test for uboot.
Here is the command we send:
timer start && nand read \${TMPADDR} ${nand_offset} \${TMPSIZE} && timer get || run fail
And below is what we get.
In the traces, after the "524288 bytes read: OK", there is the timer info: 0.080.
We need to be able to catch this value and we need to perform computation on it and some comparison afterwards.
Do you have a solution to do that?
What would you advise us to do?
Thanks a lot for your help!
Best regards,
Roselyne Mazières
[cid:image001.png@01D837B6.3FFE36F0]
Internal
Hello everyone,
I'm new to LAVA and I have some issue with 'iso-installer' for ubuntu 20.04
. As you know, in ubuntu 20.04 the preseed file would not use
'debian_installer' and use 'subiquity' instead, Also LAVA does not support
'subiquity' for 'iso-installer', so I don't know how can I use
'iso-installer' for testing my ubuntu 20.04.
Dear Lava-Team,
I contacted you a few weeks ago for some help with the integration of a new device. We got a bit further thanks to you but we're faceing some new issues and we hoped that you could help us with this.
We are using the official Docker-Compose<https://git.lavasoftware.org/lava/pkg/docker-compose> repository and specified a new device dictionary on the server container. As a device type we use a newly created device type that extends base-fastboot device-type, which looks like this:
{% extends 'rse22.jinja2' %}
{% set power_on_command = 'python ./root/power-control/ppson.py' %}
{% set power_off_command = 'python ./root/power-control/ppsoff.py' %}
{% soft_reboot_command = 'reboot' %}
{% hard_reset_command = 'python ./root/power-control/ppsoff.py && sleep 5 && python ./root/power-control/ppson.py' %}
{% set connection_list = [uart0] %}
{% set connection_commands = {uart0: telnet <ip_host_machine> 7101} %}
{% set connection_tags = {uart0: [primary, 'telnet']} %}
But with this we received the following error:
[cid:image001.png@01D6EE7C.31C35A90]
The error disappeared however when we removed the following lines:
{% set power_on_command = 'python ./root/power-control/ppson.py' %}
{% set power_off_command = 'python ./root/power-control/ppsoff.py' %}
{% soft_reboot_command = 'reboot' %}
{% hard_reset_command = 'python ./root/power-control/ppsoff.py && sleep 5 && python ./root/power-control/ppson.py' %}
With those lines we are trying to trigger the scripts, which control our power supply directly. Do we have to pay attention to the python dependencies in the scripts or could the error be in the definition itself?
We thought, that we had at least configured the device dictionary sufficiently to have a connection to the device and start a very basic health check. Our device runs Linux, which is running Android on top. The Ser2Net connection has been configured according to the instructions on the repo as well (using the telnet command by itself worked fine).
So we specified the health check like this:
device_type: rsu
job_name: Health Check for RSU
timeouts:
job:
minutes: 30
action:
minutes: 5
connection:
minutes: 2
priority: medium
visibility: public
actions:
- deploy:
namespace: tlxc
timeout:
minutes: 5
to: lxc
packages:
- android-tools-adb
- android-tools-fastboot
- boot:
method: lxc
prompts:
- 'root@(.*):/#'
timeout:
minutes: 5
- test:
timeout:
minutes: 4
definitions:
- repository:
metadata:
format: Lava-Test Test Definition 1.0
name: hello-world
description: "say hello"
os:
- android
scope:
- functional
run:
steps:
- apt -q update
- pwd
- echo "echo hello"
# remember to use -y to allow apt to proceed without interaction
# -q simplifies the apt output for logging.
from: inline
name: hello-world
path: inline/hello-world.yaml
When executing, we got the following error:
[cid:image002.png@01D6EE7E.9CED3690]
Could you please give us some advice, on how to define a test job/health check for a device, which uses fast-boot and Android?
Your help would be greatly appreciated.
Best regards,
Marcel
_________________________________________________________
EMAIL LEGAL MENTION / DISCLAIMER
This message contains information that may be privileged or confidential and is the property of the Expleo Services SAS, RCS Versailles 831 178 348, located, 3 avenue des Pr?s, 78180 Montigny Le Bretonneux - France. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
Ce message contient des informations qui peuvent ?tre privil?gi?es ou confidentielles et elles sont de la propri?t? d'Expleo Services SAS, RCS Versailles 831 178 348, situ?, 3 avenue des Pr?s, 78180 Montigny le Bretonneux-France. Il est destin? uniquement ? la personne ? qui est adress?. Si vous n'?tes pas le destinataire vis?, vous n'?tes pas autoris? ? lire, imprimer, conserver, copier, diffuser, distribuer ou utiliser ce message ou toute partie de celui-ci. Si vous recevez ce message par erreur, veuillez en avertir imm?diatement l'exp?diteur et supprimer toutes les copies de ce message.
Dear LAVA-Team,
We have only recently started to use LAVA in a new project and we are now at the point of integrating a new device. As I have read in the documentation that this is the hardest part I would like to ask for some advice where to start and what to especially look out for.
The current state is that LAVA, as a master and one slave is running in two Docker containers by using the example of the following Github repository:
https://github.com/kernelci/lava-docker
After reading the documentary extensively and trying things out with qemu I'd like to try and integrate the following device:
https://www.lantronix.com/products/sa8155p-automotive-development-platform/
Our plan so far would be:
Since it has a Snapdragon processor, it's running Android and it is using fastboot for flashing, we figured we could use one of the dragonboard Device-Type templates and duplicate it for our device. But as it comes now to configuring the device dictionary and specifying the test jobs we are not so sure as how to proceed and we also don't want to damage the hardware, so we would be grateful for some help.
Here some more information:
The DUT is connected via USB and its power supply can be turned on and off by using Python scripts (When defining the power_on and power_off commands, should the scripts then be on the master or on the dispatcher? And what are all the necessary parameters for the power on/off and also the values connection_list and connection_commands?).
It is running Android with the underlying Linux configured especially for the hardware, so we would like to avoid deploying for the beginning and only run some simple shell tests to see if the connection stands.
A very simple health check has been set up here<https://paste.debian.net/1175549>, maybe you could give some feedback if that would be sufficient and how future test jobs should be altered.
Hope to hear from you soon
Best Regards,
_________________________________________________________
EMAIL LEGAL MENTION / DISCLAIMER
This message contains information that may be privileged or confidential and is the property of the Expleo Services SAS, RCS Versailles 831 178 348, located, 3 avenue des Pr?s, 78180 Montigny Le Bretonneux - France. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
Ce message contient des informations qui peuvent ?tre privil?gi?es ou confidentielles et elles sont de la propri?t? d'Expleo Services SAS, RCS Versailles 831 178 348, situ?, 3 avenue des Pr?s, 78180 Montigny le Bretonneux-France. Il est destin? uniquement ? la personne ? qui est adress?. Si vous n'?tes pas le destinataire vis?, vous n'?tes pas autoris? ? lire, imprimer, conserver, copier, diffuser, distribuer ou utiliser ce message ou toute partie de celui-ci. Si vous recevez ce message par erreur, veuillez en avertir imm?diatement l'exp?diteur et supprimer toutes les copies de ce message.
