Device is RAM, directly connected to the FT4232H through JTAG, FT4232T connected to the windows host through USB-MicroUsb, the windows host provides the telnet test command interface to the workers of the lava automated test environment through the telnet server, in this scenario, how to create the device type, device and job in lava, Can you use lava to automate testing of RAM?
Because our system needs to save some content when rebooting, I hope to test this function, such as rebooting 5000 times, but I don’t know how to add a loop to lava device (jinja2) or job (yaml).
I find the file https://github.com/Linaro/lava-test-plans/blob/master/lava_test_plans/testc…, It looks like the "-boot" action can be controlled through a for loop.
{% for index in range(1,8) %}
{% with FASTBOOT_COMMANDS=Null %}
- boot:
{% include "include/boot_target/boot_target.jinja2" %}
{% endwith %}
{% with test_timeout=boottime_timeout %}
{% include "include/test_target.jinja2" %}
{% endwith %}
But when I try the following code,
{% for index in range(1,8) %}
- boot:
method: minimal
timeout:
minutes: 10
auto_login:
login_prompt: 'tegra-ubuntu login:'
username: root
password_prompt: "Password:"
password: "root"
login_commands:
- ifconfig
prompts:
- 'root@tegra-ubuntu:'
parameters:
kernel-start-message: ''
transfer_overlay:
download_command: cd /tmp ; wget
unpack_command: tar -m -C / -xzf
{% endfor %}
lava report error: line22 is "{% for index in range(1,8) %}"
Invalid definition: Loading job submission failed: while scanning for the next token found character that cannot start any token in "", line 22, column 2.
Where did I go wrong?
I tried to get help from lava-users(a)lists.lavasoftware.org but never got a reply,
link: https://lists.lavasoftware.org/archives/list/lava-users@lists.lavasoftware.…
Hi Team,
I was running the lava jobs and I found a difference in the status after
job completion with failures. There were failures in
i) The interactive test and lava overlay test [cases] but still the status
of the job shows as "COMPLETE".
ii) I tried an action failure retry, when action failure for the
first time, it shows the result as failure but job status as complete. The
retry- failure status should be ignored if it fails for the first time. I
convert the test results into JUNIT using rest api. In the junit result it
displays failure for the test case.
My question is, How can we customize the status of the job or ignore the
test result in case of failure-retry?
Any Advice please.
Best Regards
*Pavan Kumar*
Hello Team,
I was trying to flash a binary on the device and run the tests on the
device by using lava overlay.
Board flashes successfully but while booting the device in the boot log
there is a word "*** Invalid partition 3 ***" lava catches the key word
and throws an error message.
For the other devices it is not catching this error with the same boot log.
Only on one device I'm observing this issue.
Please let me know How to ignore the keyword and move on to run the tests.
matched a bootloader error message: 'Invalid partition' (17)
boot log:
*U-Boot SPL 2022.04 (Nov 30 2023 - 20:10:15
+0000)power_bd71837_initDDRINFO: start DRAM initDDRINFO: DRAM rate
1600MTSDDRINFO:ddrphy calibration doneDDRINFO: ddrmix config doneNormal
BootTrying to boot from MMC1hab fuse not enabledAuthenticate image from DDR
location 0x401fcdc0...NOTICE: BL31:
v2.6(release):lf-5.15.32-2.0.0-0-gc6a19b1a3-dirtyNOTICE: BL31: Built :
06:37:22, Jun 7 2022U-Boot 2022.04 (Nov 30 2023 - 20:10:15 +0000)CPU:
i.MX8MMD rev1.0 1600 MHz (running at 1200 MHz)CPU: Industrial temperature
grade (-40C to 105C) at 44CReset cause: PORModel: DRAM: 224
MiBboard_initCore: 61 devices, 21 uclasses, devicetree: separateMMC:
FSL_SDHC: 0Loading Environment from nowhere... OKIn: serialOut:
serialErr: serialSEC0: RNG instantiated BuildInfo: - ATF c6a19b1facmod
value is 1!pulse number is 0�flash target is MMC:0Fastboot: NormalNormal
BootHit any key to stop autoboot: 2 end: 3.4.2 bootloader-interrupt
(duration 00:00:05) [common]start: 3.4.3 bootloader-commands (timeout
00:02:52) [common]Setting prompt string to ['=>']bootloader-commands: Wait
for prompt ['=>'] (timeout 00:02:52) 0 Setting prompt string to
['=>']Sending with 5 millisecond of delaysetenv factorymode 1u-boot=>
setenv factorymode 1bootloader-commands: Wait for prompt ['=>'] (timeout
00:02:51)setenv factorymode 1Sending with 5 millisecond of
delaybootu-boot=> bootboot** Invalid partition 3 **Couldn't find partition
mmc 0:3Can't set block deviceuEnv not found in mmcpart3, checking
mmcpart1Failed to load '/boot/system/uEnv'uEnv not found in mmcpart 1
either!Booting from mmc ...## Error: \"w\" not definedmatched a bootloader
error message: 'Invalid partition' (17)end: 3.4.3 bootloader-commands
(duration 00:00:02) [common]case: bootloader-commandscase_id:
204071definition: lavaduration: 1.52extra: ...level: 3.4.3namespace:
commonresult: fail*
Best Regards
Pavan Kumar
Hi all,
We've been noticing an increase in a particular error, reported as a
lava bug by lava itself. An example job is
https://lava.collabora.dev/scheduler/job/10987740 - however, for
contrast, the following job, which is based on the same template,
succeeds https://lava.collabora.dev/scheduler/job/11017230.
Is this genuinely a LAVA bug or do we have a job definition problem?
Thanks
Dave
--
Dave Pigott
Principal Engineer
Collabora Ltd.
Platinum Building, St John's Innovation Park, Cambridge CB4 0DS, UK
Registered in England & Wales, no. 5513718
Hello Team,
I'm using notify action in the job definition to notify users about the
status of the job. I'm already a registered user in lava and after
completion of my job, the administration site shows the status as "*not
sent*".
Please let me know what can be the reason, and how can i achieve it?
[image: lava-notify.PNG]
Below is the job definition i'm using:
*device_type: ADT-UNIT1job_name: sample test to notify usertimeouts: job:
minutes: 15 action: minutes: 10 connection: minutes: 5visibility:
publicactions:- command: name: relay_pwr_on timeout:
minutes: 1- deploy: to: flasher images: package:
url:
https://artifactory.softwaretools.com/artifactory/gop-generic-stable-local/…
<https://artifactory.softwaretools.com/artifactory/gop-generic-stable-local/…>-
boot: method: u-boot commands: - setenv factorymode 1 -
boot auto_login: login_prompt: 'login:' username: root
password_prompt: 'Password:' password: root login_commands:
- touch /home/root/test_file - ifconfig prompts: -
'root@hon-grip' - 'root@GRIP'notify: recipients: - to: method:
email user: pavan criteria: status: finished verbosity: verbose*
Thanks & Regards,
Pavan
Hi
Can anyone have a look at the log and suggest what can be done?
Thanks & Regards
*Pavan Kumar*
On Sun, May 21, 2023 at 1:18 PM pawanKumar <pawan4749(a)gmail.com> wrote:
> Hi All,
>
> Thanks for your reply!
>
> I have pasted the log in the link below
> https://pastebin.com/qquMLthi
>
> After the boot completion I have to press "enter" manually to see the
> login prompt. If didn't press any key then it gets disconnected after some
> time. That's how the device is designed.
> By using the job definition it Enter to u-boot and send boot command
> successfully but fails while login as it doesn't see any login prompt.
> Any one please check the log and suggest whether need to make any changes
> in base file or base-uboot file.
> Since it's a new device connecting to existing lava setup I was confused a
> bit.
>
>
>
> Thanks
> *Pavan Kumar*
>
> Show quoted text
>
>
> On Thu, 18 May, 2023, 11:23 am Stefan, <
> lists.lavasoftware.org_23(a)green-sparklet.de> wrote:
>
>> Hi Pavan,
>>
>> if there's really no difference, then you are not using the correct
>> string. Is the prompt really "press enter", or might it be that it is like
>> "Press ENTER to activate this console" or "Please press Enter to activate
>> this console"? That's a difference. You need to use a string that your
>> device really displays on console.
>>
>> Regards
>> Stefan
>>
>> On 2023-05-18 07:30, pawanKumar wrote:
>>
>> Hi Stefan,
>>
>> Did you mean
>> auto_login:
>> login_prompt: "press enter"
>>
>> I tried it but there is no difference, it results in the same error.
>> Any suggestions?
>>
>> Best Regards
>> *Pavan Kumar*
>>
>>
>> On Wed, May 17, 2023 at 10:58 AM Stefan <
>> lists.lavasoftware.org_23(a)green-sparklet.de> wrote:
>>
>>> Hi Pavan,
>>>
>>> what happens if you set the 'login_prompt' to (parts of) that "press
>>> enter" string?
>>> Sure it doesn't work currently, because the string you configured
>>> doesn't get displayed
>>>
>>> Stefan
>>>
>>>
>>> Am 17. Mai 2023 07:00:31 MESZ schrieb pawanKumar <pawan4749(a)gmail.com>:
>>>
>>>> Hi
>>>>
>>>> The auto-login feature is not working here, job is failing with "*wait
>>>> for Prompt timed out*".
>>>> As I mentioned in a previous email, after completion the log login
>>>> prompt is not displayed automatically and you need to press enter key to
>>>> see the login prompt.
>>>>
>>>> Below is the definition I'm using:
>>>>
>>>> device_type: DEVICE-TYPE1
>>>> job_name: boot the device
>>>> timeouts:
>>>> job:
>>>> minutes: 15
>>>> action:
>>>> minutes: 10
>>>> connection:
>>>> minutes: 5
>>>> visibility: public
>>>> actions:
>>>> - command:
>>>> name: relay_pwr_on
>>>> timeout:
>>>> minutes: 1
>>>> - boot:
>>>> method: u-boot
>>>> commands:
>>>> - boot
>>>> auto_login:
>>>> login_prompt: 'rezi-703683 login:'
>>>> username: root
>>>> login_commands:
>>>> - touch /home/root/test_file
>>>> - ifconfig band0
>>>> - cat /etc/os-release
>>>> prompts:
>>>> - 'root@rezi'
>>>> - '#'
>>>> [image: prompt-timeout.PNG]
>>>> Best Regards
>>>> *Pavan Kumar*
>>>>
>>>>
>>>> On Tue, May 16, 2023 at 12:53 PM Remi Duraffort <
>>>> remi.duraffort(a)linaro.org> wrote:
>>>>
>>>>>
>>>>>
>>>>> Le lun. 15 mai 2023 à 11:32, pawanKumar <pawan4749(a)gmail.com> a
>>>>> écrit :
>>>>>
>>>>>> Hi Stefan,
>>>>>>
>>>>>> It means after the boot process completion, i should press "enter"
>>>>>> then only it displays a login prompt to pass username then enters into the
>>>>>> system.
>>>>>>
>>>>>
>>>>> As answered by stefan, using auto-login feature should work.
>>>>>
>>>>>
>>>>>>
>>>>>> Please check the attachment.
>>>>>>
>>>>>>
>>>>>> Best Regards
>>>>>> *Pavan Kumar*
>>>>>>
>>>>>>
>>>>>> On Mon, May 15, 2023 at 1:22 PM Stefan <
>>>>>> lists.lavasoftware.org_23(a)green-sparklet.de> wrote:
>>>>>>
>>>>>>> Hey Pavan kumar,
>>>>>>>
>>>>>>> what do mean by "after U-Boot process completion"? What does your
>>>>>>> config look like? Are you still in U-Boot, or did you already boot up your
>>>>>>> system?
>>>>>>>
>>>>>>> For the first one, it would help to modify |'||base_uboot_bootcmd'
>>>>>>> which can be overridden in your device template.
>>>>>>>
>>>>>>> If your system is already booted up, it would be up to auto_login <
>>>>>>> https://docs.lavasoftware.org/lava/actions-boot.html#auto-login> to
>>>>>>> be configured properly and take over.
>>>>>>>
>>>>>>> Regards
>>>>>>> Stefan
>>>>>>> |
>>>>>>> On 5/15/2023 9:29 AM, pawanKumar wrote:
>>>>>>> > Hello Team,
>>>>>>> >
>>>>>>> > Good Day to you!
>>>>>>> >
>>>>>>> > I have a requirement to pass "enter" key after u-boot process
>>>>>>> completion, to enter into the system.
>>>>>>> > Without pressing any key cannot enter into prompt and it stays
>>>>>>> stagnant.
>>>>>>> >
>>>>>>> > Please let me know how to pass "enter" press key at the end of
>>>>>>> u-boot log.
>>>>>>> >
>>>>>>> >
>>>>>>> > Thanks
>>>>>>> > Pavan kumar
>>>>>>> >
>>>>>>> > _______________________________________________
>>>>>>> > Lava-users mailing list -- lava-users(a)lists.lavasoftware.org
>>>>>>> > To unsubscribe send an email to
>>>>>>> lava-users-leave(a)lists.lavasoftware.org
>>>>>>> > %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Lava-users mailing list -- lava-users(a)lists.lavasoftware.org
>>>>>>> To unsubscribe send an email to
>>>>>>> lava-users-leave(a)lists.lavasoftware.org
>>>>>>> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
>>>>>>
>>>>>> _______________________________________________
>>>>>> Lava-users mailing list -- lava-users(a)lists.lavasoftware.org
>>>>>> To unsubscribe send an email to
>>>>>> lava-users-leave(a)lists.lavasoftware.org
>>>>>> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Rémi Duraffort
>>>>> Principal Tech Lead
>>>>> Automation Software Team
>>>>> Linaro
>>>>>
>>>> _______________________________________________
>>> Lava-users mailing list -- lava-users(a)lists.lavasoftware.org
>>> To unsubscribe send an email to lava-users-leave(a)lists.lavasoftware.org
>>> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
>>
>>
>> _______________________________________________
>> Lava-users mailing list -- lava-users(a)lists.lavasoftware.org
>> To unsubscribe send an email to lava-users-leave(a)lists.lavasoftware.org
>> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
>>
>>
>> _______________________________________________
>> Lava-users mailing list -- lava-users(a)lists.lavasoftware.org
>> To unsubscribe send an email to lava-users-leave(a)lists.lavasoftware.org
>> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
>
>
Hello Team,
Good Day to you!
I have a requirement to pass "enter" key after u-boot process completion,
to enter into the system.
Without pressing any key cannot enter into prompt and it stays stagnant.
Please let me know how to pass "enter" press key at the end of u-boot log.
Thanks
Pavan kumar
Hey there!
LAVA documentation at https://validation.linaro.org/static/docs/v2/contribution.html#creating-a-g… describes how to create an account and request fork permissions. Sadly the step to request fork permissions doesn't work as I can't file that requested issue to ask for access as after some days my GitLab account still yields this message at login: »Your account is pending approval from your GitLab administrator and hence blocked. Please contact your GitLab administrator if you think this is an error.« - without explanation on how to contact that administrator.
So how is the process of contributing thought to happen?
Can someone please forward this to that »GitLab administrator« so he can sort this out and get in contact with me?
Thanks in advance
Stefan
Hi All,
I'm looking to automate overall testing process and post the test results
in to JIRA instead of going to Lava CI.
Is there any way that I can use robot framework to run the tests on Lava
and so robot framework produces results in XML file that can be used to
post into issue tracker.
Any suggestions would be helpful
Thanks,
Pavan
Hello Team,
Good Day to All!
We are setting up a new device into LAVA Automation with the following
requirements.
Flash panel to R4 image
Copy delta to R5
Deploy R5
reboot
Make sure the panel boots to R5
The Test definition i'm using is as follows:
actions:
- deploy:
to: flasher
images:
package:
url:
https://artifactory.softwaretools.com/artifactory/mfgtools-***-0v3
- boot:
timeout:
minutes: 15
commands:
- boot
method: u-boot
prompts:
- 'root@hon-grip'
auto_login:
login_prompt: 'login: '
username: root
password_prompt: 'Password:'
password: root
login_commands:
- coredump --enable
- sysinfo
- ifconfig
- networkctl status
- wget http://192.100.**.**/oslat
- ostree static-delta apply-offline /home/root/oslat
- ostree admin deploy
35b3297cf3e4bc59d2a21e2ae9f7a02ef3f7a940e37389a7e9ae66a610c60b7
- reboot
After reboot command is executed, the panel again prompts for login and
password, whereas I cannot declare auto_login for the second time.
Please let me know how to disable auto login after the reboot (for second
time login)
Best Regards
*Pavan Kumar*
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.
++ Lava-users list.
Regards,
Koti
On Fri, 4 Dec 2020 at 17:30, <lava-devel-request(a)lists.lavasoftware.org>
wrote:
> Send Lava-devel mailing list submissions to
> lava-devel(a)lists.lavasoftware.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.lavasoftware.org/mailman/listinfo/lava-devel
> or, via email, send a message with subject or body 'help' to
> lava-devel-request(a)lists.lavasoftware.org
>
> You can reach the person managing the list at
> lava-devel-owner(a)lists.lavasoftware.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Lava-devel digest..."
>
>
> Today's Topics:
>
> 1. Integration of a new device (Marcel Trattner)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 4 Dec 2020 10:50:08 +0000
> From: Marcel Trattner <marcel.trattner(a)expleogroup.com>
> To: "Lava-devel(a)lists.lavasoftware.org"
> <Lava-devel(a)lists.lavasoftware.org>
> Cc: Alexander Wyron Wachtberger
> <alexander-wyron.wachtberger(a)expleogroup.com>, Vladimir Schmidt
> <vladimir.schmidt(a)expleogroup.com>
> Subject: [Lava-devel] Integration of a new device
> Message-ID:
> <
> AM9PR10MB4295B7516795BD7B514C2DF7E5F10(a)AM9PR10MB4295.EURPRD10.PROD.OUTLOOK.COM
> >
>
> Content-Type: text/plain; charset="us-ascii"
>
> 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.
>
