linaro-validation September 2013

linaro-validation@lists.linaro.org

18 participants
16 discussions

LAVA upgrade for 64-bit models support...

by Basil Eljuse

Hi Dave, I am hoping that probably you might be working on this ticket https://cards.linaro.org/browse/CARD-832 (got from Kanta, although I get permission denied when accessing the card), if not please anyone in the wider validation email group please redirect me appropriately. With 13.09 we do have the new Base model variants released and with the above ticket we expect to have LAVA support for these models also. Since we do have a local LAVA instance, I would like to figure out how we can pick the upgrades and apply to our local instance. Could anyone please advice when we could expect this upgrade to LAVA for supporting 64-bit base models, coming our way? I want to get Dean a heads-up in terms of his plan to get our setup upgraded. Thanks Basil Eljuse... -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2557590 ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2548782

10 years, 6 months

Re: [Linaro-validation] [LNG] run BE in lava

by Fathi Boudra

CC'ing LAVA guys On 26 September 2013 15:46, Maxim Uvarov <maxim.uvarov(a)linaro.org> wrote: > As I understand this log right: > https://validation.linaro.org/scheduler/job/74753/log_file > > Arndale booted with standard LE rootfs. Then there is wget rootfs and chroot > to it. > And of course any commands under chroot will fail. > > So I think for now it's impossible to run BE in lava boards unless we will > set up any board with > BE env or remove chroot from set up scripts. > > Is chroot really needed for this? : > chroot /mnt/root ln -sf /bin/true /usr/sbin/flash-kernel > > Thank you, > Maxim.

10 years, 6 months

[ANN] LAVA development moves to git

by Antonio Terceiro

Hello everyone, TL;DR: as announced previously [1], since today LAVA development happens on git. Some points I would like to highlight: - Please do not send bzr merge proposals against the old bzr repositories on Launchpad. In the next days those repositories will be closed down (assuming that's at all possible - any tips appreciated) to make it impossible for people to send those. - The procedure for submitting changes to LAVA is now using the gerrit instance at staging.review.linaro.org, which should be available as review.linaro.org at some point in the future. As mentioned previously, we are dogfooding the system before providing it as an official service for the wider community, so bear with me and please let us know of any problems or questions you might have. Documentation for staging.review.linaro.org is available at: https://wiki.linaro.org/Platform/LAVA/Infrastructure/StagingReview - the source for source code is git.linaro.org, under the lava/ namespace. As we already discussed, the LAVA team will be actually using staging.git.linaro.org as part of the aforementioned dogfooding exercise. However we configured sync on push in the lava repositories so that git.linaro.org and staging.git.linaro.org will always contain exactly the same code. - Launchpad is still used for bug management. Please continue submitting bugs there. - Unrelated to the move to git, you will notice two important changes in LAVA that I think it's useful to mention: The first change is that now we have a new theme[2] which IMO makes LAVA look a lot nicer. It's not a designer's job, but is an improvement. ;-) The second change is that now every LAVA instance hosts full documentation _generated from the actual code it is running_, linked from the "Documentation" link in the top menu[3]. It's still the same old documentation we had before on .readthedocs.org, but this is just the first visible step of the effort the LAVA team is putting in the documentation area. Expect exciting news about this in the future. 1. http://lists.linaro.org/pipermail/linaro-validation/2013-September/002067.h… 2. see it for yourself at http://validation.linaro.org/ 3. e.g. http://validation.linaro.org/static/docs/ Cheers, -- Antonio Terceiro Software Engineer - Linaro http://www.linaro.org

10 years, 6 months

target login

by novello giampiero

SORRY i need some information: a) There is a way to answer the the login and password of the target via lava-dispatcher? b)I 'm making a new configuration file for wandboard is better to use master or client_type = bootloader client_type = master in the wand.conf file? Best regards Novello G.

10 years, 6 months

Your start times may vary

by Dave Pigott

Hi all, My wife is currently at the hospital with a broken toe or toes. I'm home baby sitting and have no idea when she'll be back. On that basis I have no idea if/when I'll be in the office tomorrow. Thanks Dave

10 years, 7 months

lava_command_run command on the dispacher?

by Novello Giampiero

Sorry I see in internet that there i a new command in lava-dispacher. This command si : LAVA_COMMAND_RUN. My questio is: does thi command work with a dummy_deploy in a test.json There are some examples available? Best regards Novello G.

10 years, 7 months

usage of lava-dispacher in an custom filesystem on wandaboard

by novello giampiero

Is there any reason why you took this off the mailing list? If not, can you please post your message there instead, so other people can also benefit from the discussion? On Sun, Sep 22, 2013 at 09:06:59PM +0200, Novello Giampiero wrote: > I have 2 board with sa same (imx wandboard and pandaboard) > In any case I have the same result. > I have made a wand.conf and a wand01.conf > Wand.conf file is very similar to pand.conf file, > Here you will se the logfile . > lava-dispatch /../wand6.json --target wand01 | tee logfile > > I you can see in the log file I can't download the file. > In the file system for the wandboard there is LAVA-TEST and it work! > I have installed in pc with ubuntu 12.04 the lastest version of > lava-deployment-tool from git. > In the target device I have installed python, wget,git etc I don't know if > I have to install some other package (lighthttpd) or if I have to install > Apache. At the moment lava-dispatcher assumes there is python in the master image, because the webserver used on the target to allow the dispatcher do download contents of the filesystem is started with: python -m SimpleHTTPServer 0 2>/dev/null The master images we use at Linaro do have Python, even though the test images might not have it. But since you are using dummy deploy, you will probably have to install python. This should be changed to use `busybox httpd` at some point, but we are not there yet. On The Target I Have Python 2.7 installed end the lava-test Those test work well. If In the target from the shell I DO: python -m SimpleHTTPServer 0 2>/dev/null in the HOST I CAN OPEN FIREFOX AND THEN DOWNLOAD FS.TGZ. In the other case I have the mistake that you can see in the log files. Do you have some IDEA? PS.:I'm using Master.py like pandaboard. MAy I change some think in the wand01.conf? Best Regards Novello G --

10 years, 7 months

reboot after installing dependencies?

by Milosz Wasilewski

Hi, Is it possible in LAVA to force reboot between installing test case dependencies and running the test itself? I'm trying to run bootchart test, but the bootchart package is not included in the ubuntu image I'm running. Best Regards, milosz

10 years, 7 months

request of information

by novello giampiero

I ' m traying to use lava-dispscher to test a yocto made filesystem for pandaboard. My question is ther is a file that describe what i need to install in the file open embedded filesystem? I have installed lava-test that work. I would like to manage the board from the "dispacher". lava-dispach /.../test.json --target panda01 Best regards Novello G

10 years, 7 months

Re: [Linaro-validation] "android_install_binaries" failure after "deploy_linaro_android_image"

by Leo Wu

Hi Tyler: Thanks your information, it is useful. For current status, i can pass "android_install_binaries" but getting stuck in "boot_linaro_android_image". I think the problem is still relevant to panda-driver. This web have four files about pandaboard driver you posted( https://developers.google.com/android/nexus/drivers) 20111114 20111216 20120430 20120807 i dont know which one is suitable for my pandaboard so i have tried everyone. There have no one can pass "boot_linaro_android_image". The Log as following... LOG: 20111114: [ 521.131805] PVR_K:(Error): BridgedDispatchKM: Initialisation failed. Driver unusable. [4812, /mnt/jenkins/workspace/linaro-android-member-ti_panda-linaro-13.02-release/build/kernel/drivers/gpu/pvr/bridged_pvr_bridge.c] [ 521.202728] PVR_K:(Error): BridgedDispatchKM: Initialisation failed. Driver unusable. [4812, /mnt/jenkins/workspace/linaro-android-member-ti_panda-linaro-13.02-release/build/kernel/drivers/gpu/pvr/bridged_pvr_bridge.c] [ 521.552642] init: untracked pid 3766 exited [ 521.626464] init: untracked pid 3762 exited LEO COMMENT: PVR_K error. Does this driver not suitable for my pandaboard? 20111216 linaro-13.02-release/build/kernel/drivers/gpu/pvr/bridged_pvr_bridge.c] [ 37.700134] PVR_K:(Error): BridgedDispatchKM: Initialisation failed. Driver unusable. [4812, /mnt/jenkins/workspace/linaro-android-member-ti_panda-linaro-13.02-release/build/kernel/drivers/gpu/pvr/bridged_pvr_bridge.c] [ 38.766967] init: untracked pid 1771 exited [ 41.124938] init: untracked pid 1774 exited LEO COMMENT: It looks like same as 20111114. 20120430: <LAVA_DISPATCHER>2013-03-27 02:30:45 PM DEBUG: expect (1800): '['Displayed com.android.launcher/com.android.launcher2.Launcher:']' logcat -s ActivityManager:I --------- beginning of /dev/log/main --------- beginning of /dev/log/system [ 96.093536] warning: `zygote' uses 32-bit capabilities (legacy support in use) I/ActivityManager( 1776): Memory class: 48 I/ActivityManager( 1776): Enabled StrictMode logging for AThread's Looper LEO COMMENT: No error message on this version. But it hang up and no more message print out. No console command line when i click "enter" key. 20120807: [ 53.677490] PVR_K:(Error): BridgedDispatchKM: Driver initialisation not completed yet. [4836, /mnt/jenkins/workspace/linaro-android-member-ti_panda-linaro-13.02-release/build/kernel/drivers/gpu/pvr/bridged_pvr_bridge.c] [ 53.737884] PVR_K:(Error): BridgedDispatchKM: Driver initialisation not completed yet. [4836, /mnt/jenkins/workspace/linaro-android-member-ti_panda-linaro-13.02-release/build/kernel/drivers/gpu/pvr/bridged_pvr_bridge.c] [ 54.163696] init: untracked pid 1781 exited [ 55.792907] init: untracked pid 1784 exited LEO COMMENT: It looks like same as 20111114. One thing need to be mentiond, there have no "pvrsrvinit" but "pvrsrvctl" in version 20120807. Both files are same? LEO On 26 March 2013 20:57, Tyler Baker <tyler.baker(a)linaro.org> wrote: > Hi Leo Wu, > > The "android_install_binaries" dispatcher command will download, unpack, > and deploy proprietary shared objects to the Android file system. > > You can get these binaries from here: > https://developers.google.com/android/nexus/drivers - Choose the correct > binaries based on your Android build target. > > You will then have to create the following directory structure and tgz it: > > ./bin: > pvrsrvinit > > ./vendor: > lib > > ./vendor/lib: > egl hw libglslcompiler.so libIMGegl.so libpvr2d.so > libpvrANDROID_WSEGL.so libPVRScopeServices.so libsrv_init.so > libsrv_um.so libusc.so > > ./vendor/lib/egl: > libEGL_POWERVR_SGX540_120.so libGLESv1_CM_POWERVR_SGX540_120.so > libGLESv2_POWERVR_SGX540_120.so > > ./vendor/lib/hw: > gralloc.omap4.so > > At this point you have created your own panda-driver.tgz > > Now you will need to host it on a web server/file system that your LAVA > server can access. > > For instance, my LAVA server has the following defined: > > android_binary_drivers = http://192.168.1.2/panda-drivers.tgz <-- You > have to host this URL > > Hopefully this clears up any confusion you may have. Thanks. > > > > > > > On 26 March 2013 02:15, Leo Wu <leo.wu(a)linaro.org> wrote: > >> hi: >> Does anyone knows how to use "android_install_binaries" command in json >> file? Please give me some suggestion. >> I am trying to perfome lava android test on pandaboard. Currently, i face >> a problem while json file execute "android_install_binaries". >> The log shows it tries to connect to >> http://192.168.1.21/LAVA_HTTP/android-binaries/panda-drivers.tgz. >> >> log: http://192.168.1.21/LAVA_HTTP/android-binaries/panda-drivers.tgz Connecting >> to 192.168.1.21:80... failed:Connection timed out. >> RuntimeError: Extracting >> http://192.168.1.21/LAVA_HTTP/android-binaries/panda-drivers.tgz on >> target failed >> >> LAVA SERVER IP: 222.222.222.4 >> Board: pandaboard >> Master Image: Linaro PreBuild Image >> Test Image: LEB android >> >> >> 1. My LAVA SERVER ip is 222.222.222.4. i confused that why it tries to >> connect to 192.168.1.21? >> 2. what is panda-drivers.tgz? is it exist in lava server already or i >> need to download panda-drivers.tgz from somewhere by manual and stored it >> in local at first? >> 3. how to configure it? >> >> Thank you >> Leo >> >> _______________________________________________ >> linaro-validation mailing list >> linaro-validation(a)lists.linaro.org >> http://lists.linaro.org/mailman/listinfo/linaro-validation >> >> > > > -- > Tyler Baker > Technical Architect, Automation & CI > Linaro.org | Open source software for ARM SoCs > Follow Linaro: http://www.facebook.com/pages/Linaro > http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog >

10 years, 7 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

linaro-validation September 2013