lava-users

lava-users@lists.lavasoftware.org

1 participants
919 discussions

by Milosz Wasilewski

Hi, Chase did an excellent job and put together a piece of code that allows us local execution of lava-test-shell. This means we can use our 'lava' test definitions on the boards that are not deployed in any LAB. There are 2 main reasons for doing that: - prototyping tests for LAVA - semi-automated execution of tests on targets that are not deployed in any LAB Major part of this code is taken directly from lava dispatcher. There are slight modifications but I would like to keep them to minimum or remove at all (if possible). So the question follows - is there a way to achieve the same goal with only LAVA code? One of the biggest problems was requirement for ACKing that lava-test-shell requires. This makes the tests 'interactive' which isn't best for semi-automated execution. This bit was removed and now we're able to use test shell locally in non-interactive mode. The README file describes the use cases we're covering. Any comments are welcome. Code can be found here: https://git.linaro.org/qa/lava-local-test.git milosz

8 years, 8 months

error - lava-android-test has not been installed

by Umamaheswara Rao Lankoti

Hi I created algiz device type as : client_type = fastboot fastboot_driver = fastboot adb_command = adb fastboot_command = fastboot and algiz01 device as: device_type = algiz adb_command = adb fastboot_command = fastboot created job as below: ---------------------------------------------- { "actions": [ { "command": "lava_android_test_run", "parameters": { "test_name": "ls /sdcard/" } }, { "command": "submit_results", "parameters": { "server": "http://192.168.100.84/RPC2/", "stream": "/anonymous/ulankoti/" } } ], "device_type": "algiz", "health_check": false, "job_name": "test-job-run", "logging_level": "DEBUG", "timeout": 18000 } ---------------------------------------------- Below error is coming when the job run: -------------------------------------------------------------------- Section 0<http://localhost/scheduler/job/5/log_file#L_0> 0.0<http://localhost/scheduler/job/5/log_file#L_0_0> <LAVA_DISPATCHER>2016-08-08 09:45:20 AM DEBUG: [ACTION-B] Single node test! 0.1<http://localhost/scheduler/job/5/log_file#L_0_1> <LAVA_DISPATCHER>2016-08-08 09:45:20 AM DEBUG: lmp modules default init data is [] 0.2<http://localhost/scheduler/job/5/log_file#L_0_2> <LAVA_DISPATCHER>2016-08-08 09:45:20 AM DEBUG: lmp modules final init data is [] 0.3<http://localhost/scheduler/job/5/log_file#L_0_3> <LAVA_DISPATCHER>2016-08-08 09:45:20 AM INFO: [ACTION-B] lava_android_test_run is started with {'timeout': 18000, u'test_name': u'ls /sdcard/'} 0.4<http://localhost/scheduler/job/5/log_file#L_0_4> <LAVA_DISPATCHER>2016-08-08 09:45:20 AM WARNING: pexpect timed out with status fail 0.5<http://localhost/scheduler/job/5/log_file#L_0_5> <LAVA_DISPATCHER>2016-08-08 09:45:20 AM DEBUG: finally status fail 0.6<http://localhost/scheduler/job/5/log_file#L_0_6> <LAVA_DISPATCHER>2016-08-08 09:45:20 AM WARNING: [ACTION-E] lava_android_test_run is finished with error (lava-android-test has not been installed). Section 1<http://localhost/scheduler/job/5/log_file#L_1> 1.0<http://localhost/scheduler/job/5/log_file#L_1_0> ErrorMessage: lava-android-test has not been installed 1.1<http://localhost/scheduler/job/5/log_file#L_1_1> Lava failed at action lava_android_test_run with error:lava-android-test has not been installed Section 2<http://localhost/scheduler/job/5/log_file#L_2> 2.0<http://localhost/scheduler/job/5/log_file#L_2_0> Traceback (most recent call last): 2.1<http://localhost/scheduler/job/5/log_file#L_2_1> File "/usr/lib/python2.7/dist-packages/lava_dispatcher/job.py", line 385, in run 2.2<http://localhost/scheduler/job/5/log_file#L_2_2> action.run(**params) 2.3<http://localhost/scheduler/job/5/log_file#L_2_3> File "/usr/lib/python2.7/dist-packages/lava_dispatcher/actions/lava_android_test.py", line 57, in run 2.4<http://localhost/scheduler/job/5/log_file#L_2_4> self.check_lava_android_test_installed() 2.5<http://localhost/scheduler/job/5/log_file#L_2_5> File "/usr/lib/python2.7/dist-packages/lava_dispatcher/actions/lava_android_test.py", line 34, in check_lava_android_test_installed 2.6<http://localhost/scheduler/job/5/log_file#L_2_6> raise OperationFailed('lava-android-test has not been installed') 2.7<http://localhost/scheduler/job/5/log_file#L_2_7> OperationFailed: lava-android-test has not been installed --------------------------------------------------------------------------------- I have installed lava-android-test on the host PC from git.linaro.org/lava/lava-android-test.git Device is attached to the host PC via usb and 'adb devices' lists the device. Still getting "lava-android-test has not been installed" error. Can someone help how to resolve this issue? thanks, uma..

8 years, 8 months

Re: [Lava-users] LAVA setup for continuous integration validation of Android builds

by Senthil Kumaran S

Hi Mahesh, On Tuesday 19 July 2016 05:58 PM, Umamaheswara Rao Lankoti wrote: > I am Umamaheswara Rao working for Innominds and I am trying to evaluate > LAVA framework as part of Continuous Integration job. Nice to know. > I am looking at automating the smoke tests with LAVA, downloading a > newly generated build from Jenkins, flash it on android phone, boot into > home screen and run a minimal set of usecases, report success/failure > for the test cases, etc.. There is no direct integration such as plugins which does this in LAVA. But you can submit jobs to LAVA via scripts, once the builds are ready in Jenkins. This is already done as part of many jenkin based CI loops used within Linaro and elsewhere. > Looking at the documentation, I came to know that Ubuntu support is > stopped. Would Debian Jessie be supported in future? Yes you are right Ubuntu is deprecated. Debian will be supported in future. We support Debian Jessie and Testing as of today. PS: I ve added lava-users mailing list, so that you would get more inputs on this topic, in case if I ve missed anything. Thank You. -- Senthil Kumaran S http://www.stylesen.org/ http://www.sasenthilkumaran.com/

8 years, 8 months

No GUI Environment After Lava Installation

by Luís Matallui

Hi, I've just made a fresh Debian (Jessie) installation. Then, I've added jessie-backports and installed lava-server from there. Once the installation completed, I've rebooted and the GUI desktop environment doesn't come up. This happened twice already, so it's definitely the Lava installation that's breaking something there. Is this a known issue? Any suggestions? Regards, matallui

8 years, 9 months

Boot Issue

by Albarran, Josue

Hi, I had a boot issue and it was because of using SPACE to stop the autoboot. A quick fix for this was to add a \" to a variable declaration such as "setenv dummy variable\"". Do you know of any other fix for this? It seems the default for lava is "Hit any key to stop autoboot" and just send a "b" to stop it. In my case, I had to change the device configuration file to look for "Press SPACE to abort autoboot in 2 seconds" and then send a " ". The device configuration looks as follows http://pastebin.ubuntu.com/18790420/. Now I have another issue where the job keeps going even though the image booted successfully. I want it to stop once it sees "am335x-evm login:". Is there a way to do this? I changed the master_str = am335x-evm login:. This is my complete log http://pastebin.ubuntu.com/18790288/. Thanks, Josue

8 years, 9 months

Lava: advice for server installation

by Denis HUMEAU

Dear Lava team, We're deploying Lava V2. So far we've been working on old servers to prototype our installation. We're now almost ready to order our definitive PCs. We have assessed some key features for our Lava server. Still, we're not 100% sure on how powerful it should be. Is it possible for you to share the main characteristics of your current Lava servers (Number of cores, RAM, size of disk)? That would be helpful. Thanks and best regards, Denis Humeau

8 years, 9 months

PDU and beaglebone black support in LAVA

by Albarran, Josue

Hi, I'm currently trying to configure a Switched Rack PDU to the lava instance. How do I know if the driver for my PDU APC AP7901 is supported in the framework? I got it connected both via serial and telnet. My /etc/lavapdu/lavapdu.conf file is attached. Also, when I restart the lavapdu-runner it fails with the error that is attached. As for the beaglebone black support, I have a device dictionary but where should I save it so lava can access it? I've seen that the pdu hostname is always similar to pdu05. How do I know my pdu's hostname? I appreciate the help, thanks. Regards, Josue Albarran

8 years, 9 months

Looking for suggestions for dispatcher machines

by Sandeep Chawla

Hello, I have a lava setup and right now running two single instance servers. These are pretty high end servers are handling 4-5 Android devices over USB I need to expand that to multi node setup with maximum DUTs connected to one dispatcher. The target is only to have android DUTs so that implies a very stable USB hub and stack on the dispatcher machines. I used a couple of off the shelf desktops in the past and the USB stack could not handle more than 1 device at a time. Any suggestions for hardware that is proven to be solid for dispatchers. Thanks Sandeep

8 years, 9 months

Upgrade from 2016.4 to 2016.6 breaks custom LAVA extension

by Konrad Scherer

Hello, For the 2016.4 release I had created a custom LAVA extension to add 2 commands and 2 xmlrpc methods. The extension mechanism was very convenient. All I had to do was install an egg on the system and restart the lava service. When I upgraded to 2016.6 the extension did not work due to commit b6fd045cc2b320ed34a6fefd713cd0574ed7b376 "Remove the need for extensions". I was not able to find a way to add my extension to INSTALLED_APPS and register the xmlrpc methods without modifying settings/common.py and urls.py. I looked through common.py and distro.py and could not find support in settings.conf for extensions. I also looked for a local_settings import which is referenced on the Internet as a common way to extend django, but did not find it. If there is a way to extend LAVA without modifying the LAVA python code, please let me know and I will be happy to send in a documentation patch. It would have been nice if functionality such as the extension mechanism, which is part of the external interface of LAVA, had gone through a deprecation cycle. A reworked demo app showing how the new extension mechanism works would have also been helpful. Thank you for your time. -- Konrad Scherer, MTS, Linux Products Group, Wind River

8 years, 10 months

Fwd: pipeline vland help

by Christian Ziethén

---------- Forwarded message ---------- From: Steve McIntyre <steve.mcintyre(a)linaro.org> Date: 31 May 2016 at 16:46 Subject: Re: pipeline vland help To: Christian Ziethén <christian.ziethen(a)linaro.org> Cc: neil.williams(a)linaro.org On Tue, May 31, 2016 at 03:29:45PM +0200, Christian Ziethén wrote: >Hi, Hi Christian, You'd be much better asking on the lava-users mailing list rather than just directly to me, I'll be honest. >Been struggling with setting up a vland between two arndale targets. I have >managed to create a multinode job that uses the pipeline model: >https://lng.validation.linaro.org/scheduler/job/9702/multinode_definition >Have also managed to create valid yaml that seems to conform to the code in >lava-server/lava_scheduler_app/schema.py >https://lng.validation.linaro.org/scheduler/job/9743/multinode_definition >This one does however not do anything after being submitted, I tried putting >100M in the tags for the vland, I also tried requiring that the arndale targets >in the multinode protocol had the 100M tag, but that didn't work. According to >the device dictionary for lng-arndale-01, it should have a 100M tag on iface1. Hmmm, OK. I can see that it's sat waiting for devices to be assigned. Looking at the definition, you've got one group (role) defined with 2 entries. I believe that for VLANd jobs you need to have individual roles for each machine. Neil can confirm. >Also have this job (v1): >https://lng.validation.linaro.org/scheduler/job/9118/multinode_definition >Which runs my test using iface1 (I think) but it doesn't use vland. Right, v1 doesn't do vland. >I am unsure how to debug this. > >It was my assumption that I could create a vlan with the vland protocol and >then query which interface is on that vlan in my test-definition. That would be >my end goal for this exercise. Sure, that's what we expect to have working for you. Cheers, -- Steve McIntyre steve.mcintyre(a)linaro.org <http://www.linaro.org/> Linaro.org | Open source software for ARM SoCs

8 years, 10 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

lava-users