lava-users

lava-users@lists.lavasoftware.org

2 participants
936 discussions

[PATCH] bootloader: add ramdisk_raw option

by Kevin Hilman

By default, a uboot header is automatically added to the ramdisk image. For bootloaders without INITRD_ATAG support, the ramdisk needs to be passed on the command line and cannot have the uboot header added. To enable this feature, add a "ramdisk_raw" option that device files can set so that a uboot header is not added. Signed-off-by: Kevin Hilman <khilman(a)baylibre.com> --- Patch applies on 2016.9 lava_dispatcher/config.py | 1 + lava_dispatcher/device/bootloader.py | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/lava_dispatcher/config.py b/lava_dispatcher/config.py index 66a9e70021fa..c91c5634280d 100644 --- a/lava_dispatcher/config.py +++ b/lava_dispatcher/config.py @@ -312,6 +312,7 @@ class DeviceSchema(schema.Schema): uimage_xip = schema.BoolOption(default=False) append_dtb = schema.BoolOption(default=False) prepend_blob = schema.StringOption(default=None) + ramdisk_raw = schema.BoolOption(default=False) # for dynamic_vm devices dynamic_vm_backend_device_type = schema.StringOption(default='kvm') diff --git a/lava_dispatcher/device/bootloader.py b/lava_dispatcher/device/bootloader.py index 634d22ef3311..c88fba8937e6 100644 --- a/lava_dispatcher/device/bootloader.py +++ b/lava_dispatcher/device/bootloader.py @@ -208,7 +208,7 @@ class BootloaderTarget(MasterImageTarget): decompress=False) extract_overlay(overlay, ramdisk_dir) ramdisk = create_ramdisk(ramdisk_dir, self._tmpdir) - if self._is_uboot(): + if self._is_uboot() and not self.config.ramdisk_raw: # Ensure ramdisk has u-boot header if not self._is_uboot_ramdisk(ramdisk): ramdisk_uboot = ramdisk + ".uboot" -- 2.5.0

9 years

Help: job email notification log and deivce state change command

by kingboli

Hello everyone, Can you help me on below two questions? 1. I did email notification settings for sending emails after job complete or incomplete. How can I get whole logs (where are logs?) about email sending process? I need to debug email sending. 2. I want to use script to control device state periodically. How can I set device to maintenance state using command, like lava-tool command? Thanks in advance.

9 years

lava-dispatcher and lava-tool

by alfonso

Hello everyone, just a simple question. I might be wrong but I understand that submitting a job through lava-dispatch and lava-tool should lead to the same process. Now, with the dispacher you can already specify an specific target device encoded in yaml format. Does the lava-tool at some point reach a similar target configuration? does it generate it or it is stored somewhere? in the latter case, where is it stored? thanks in advance :) Best, Alfonso

9 years

test zipped qemu image

by alfonso

Hello everyone, just a quick question. I am trying to run a job to test a qemu image which is stored remotely. The image is packed in a tar.xz file with both the kernel and the file system. is there a way to specify in the job description json file that before the deploy action it must open this tar.xz file and then use the kernel and filesystem? Thanks a lot :) Best, Alfonso

9 years

Installing on Ubuntu 16.04

by Alfonso Ros Dos Santos

Hello guys, I am currently trying to install the lava-server/dispatcher on my local pc with Ubuntu 16.04. Unfortunately, I had little success installing the source projects from github.com/linaro. I just wanted to ask if you could recommend me what would be the best approach for me. Thanks for your help. Best regards, Alfonso

9 years, 1 month

matching results to requested tests

by Milosz Wasilewski

Hi, I'm trying to get the proper relationship between requested tests and results in LAVA v2. Here is example job: https://validation.linaro.org/scheduler/job/1109234 and results for this job: https://validation.linaro.org/results/1109234 How can I tell: - which result matches which test? - if there are multiple occurrences of the same test with different parameters, how to recognize the results? In LAVA v1 the matching was a very arduous process. One had to download the job definition, look for lava-test-shell actions, pull the test definition yaml sources and match yaml ID and to ID found in result bundle. How does this work in v2? milosz

9 years, 1 month

Latest Tradefed version for Android Testing

by Sandeep Chawla

Hello, Google has release the latest version of Tradefed with the Android N release. https://source.android.com/devices/tech/test_infra/tradefed/index.html Lots of dispatcher/slave features which LAVA already supports. Given this update, is LAVA exploring to adopt the new mechanism or continue developing its own architecture ? Thanks Sandeep

9 years, 2 months

Local lava-test-shell

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

9 years, 2 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..

9 years, 2 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/

9 years, 3 months

← Newer
1
...
87
88
89
90
91
92
93
94
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

lava-users