linaro-validation

linaro-validation@lists.linaro.org

818 discussions

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.

11 years, 11 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 --

11 years, 11 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

11 years, 11 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

11 years, 11 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 >

11 years, 11 months

Announcement: LAVA migrating to git

by Antonio Terceiro

Hello everyone, TL;DR: LAVA development and deployment infrastructure will be moving to git over the course of this month. The expected cut off date is August 18th. We are starting the migrating all of the LAVA source code from bzr to git today. We planned this to happen in the least-desruptive way possible, so this will be done in a phases. The plan is the following: ----------------8<----------------8<----------------8<----------------- 1) mirror current bzr branches into git. So the first step is to make the contents of the existing bzr repos on git. This is done, and all LAVA components are available at git.linaro.org. Those repositories contain the contents of their bzr counterparts as of today, and will be updated again when we discontinue bzr. This step is already done. 2) update deployment infrastructure to use git lava-deployment-tool and lava-manifest will be branched already in their git repositories updated to pull code for the other components from git instead of bzr. This will be tested on staging, including upgrading from a bzr-based deployment to a git-based one. lava-lab (the repository where we maintain the salt configuration for the Linaro Cambridge lab) will also be switched to git at this point. Up until this phase is completed, bug fixes and updates to the official production site will still be done from bzr. 3) final bzr cut off and move to git When we are satisfied with the deployment from git branches, we will finally discontinue bzr. lava-deployment-tool and lava-manifest "deploy-from-git" branches will be merged into the respective master branches. All other components will be synced from bzr to git one last time. At this point the bzr branches on Launchpad will be officially deprecated and will probably not receive any more updates (so that getting the latest version on bzr continues to be possible). Development moves to git.linaro.org. We will continue using Launchpad for bug management. This is expected to be done by August the 18th. ----------------8<----------------8<----------------8<----------------- Please feel free to voice any concerns or questions regarding this change. -- Antonio Terceiro Software Engineer - Linaro http://www.linaro.org

11 years, 11 months

wandboar test with lava.

by Novello Giampiero

I would like to use lava-dispatch fot test this device. I Have made wand.con end wand01.con. You can see tham... To make wand.conf I was started from panda.conf making a small change #client_type = bootloader client_type = master !!! IS THIS THE BEST CHOISE??? I would like to test a OE make file system for that I Have used: wand3.json that is configured with dummy_deploy. class cmd_dummy_deploy(BaseAction): parameters_schema = { 'type': 'object', 'properties': { 'target_type': {'type': 'string', 'enum': ['ubuntu', 'oe', 'android', 'fedora']}, }, 'additionalProperties': False, } def run(self, target_type): print("deploy.py::cmd_dummy_deploy::141::run-end") device = self.client.target_device #device.boot_master_image() device.deployment_data = device.target_map[target_type] print("deploy.py::cmd_dummy_deploy::141::run-end") In deploy.py... The problem I have is that In any case a soft reset of the board is made. My question is: Is may configuration correct?? Best Regards Novello G.

11 years, 11 months

Query on UEFI SCT support on LAVA...

by Basil Eljuse

Hello All, In the recent LEG update summary I found a mention about LAVA support for UEFI SCT tests. I am quite keen to know the status of this. Is the current support for only Models or can I expect this could work on TC2 also? Keen to know the status and see if I could make use of this support internally. 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

11 years, 11 months

Xen lava job and vexpress-tc2 board setup

by Wookey

I am trying to set up a Xen CI job on lava. The components are built (Xen hypervisor, xen tools deb package, Xen-enabled kernel, standard minimal rootfs). Now I'm working out what the lava job should look like. Xen requires a non-standard boot with the hypervisor loaded as well as the kernel before booting (and rootfs unpacked). Julien says we need to do (at least some of) the config on this page before running XEN: http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/Vexpress which involves disabling the A7 (required), and one way of loading the stuff in the right places, which there may be uboot/uefi-based alternatives to?). This config is done in images.txt and board.txt files. Those files apparently live on the second, internal, microSD card. I presume that deploy_linaro_image only writes to the main SD card. Certainly the hwpack (http://releases.linaro.org/13.08/ubuntu/vexpress/hwpack_linaro-vexpress_201…) does not contain an images.txt or board.txt file) The card can apparently be exposed as a fat filesystem over USB (usb-storage). Is that cable plugged in? Is there a lava mechanism for accessing this and updating it? What firmware version (boot monitor) is in the machine in the lab? What is currently in the images.txt, board.txt files it is booting with? Is 'sys_flags' bringup already selected or not? Who knows about this stuff? If we can't change those files in lava jobs then I believe that the xen CI task is currently blocked until one of these becomes true: * Xen runs on the standard vexpress config * Xen runs on arndale properly * A mechanism for changing these files is developed The Xen card: https://cards.linaro.org/browse/VIRT-75 Wookey -- Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM http://wookware.org/

11 years, 11 months

LAVA Dashboard: test results listed but not specified

by Andrew McDermott

Hi, I was looking at the following test results summary: https://validation.linaro.org/dashboard/image-reports/leg-java-armv8 and, taking build 451, I was wondering why the following tests are listed: mysql, phpinfo, phpmysql, pwrmgmt, sdkhelloc, sdkhellocxx when they are not mentioned in the following job definition: https://validation.linaro.org/scheduler/job/70985 Looking at what was explicitly listed I see: $ grep '"testdef":' job_70985.json "testdef": "openembedded/busybox.yaml" "testdef": "openembedded/device-tree.yaml" "testdef": "openembedded/ethernet.yaml" "testdef": "openembedded/kernel-version.yaml" "testdef": "openembedded/perf.yaml" "testdef": "openembedded/toolchain.yaml" "testdef": "openembedded/openjdk7-sanity.yaml" "testdef": "openembedded/openjdk8-sanity.yaml" "testdef": "openembedded/mauve.yaml" "testdef": "openembedded/jtreg.yaml" -- andy

11 years, 11 months

← Newer
1
...
27
28
29
30
31
32
33
...
82
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

linaro-validation