linaro-validation June 2014

linaro-validation@lists.linaro.org

11 participants
21 discussions

Lava server - external tests results imported into dashboard

by Chisanovici, IonutX

Hi all, As I wrote in a previous mail, I kindly ask you to point me for some straight documentation on how we can import some external tests results directly to lava dashboard via JSON file ? I search for 2 days for documentation on how to do it but couldn't find any. Is there some step by step documentation/examples ? Thank you for the help, Ionut C

10 years, 7 months

[Activity] Week #23

by Senthil Kumaran

# Progress # * Extra meta-data population error debugging * Bug 1325714 - Workers are never marked offline * Bug 1325657 - Old workers cannot be hidden * LAVA-1344 Archive script recommended by LAVA * various code reviews * Time * Cards - 30% * Bugs - 50% * various code reviews - 20% # Plan # * pending LAVA cards * bug fixes -- Senthil Kumaran http://www.stylesen.org/ http://www.sasenthilkumaran.com/

10 years, 7 months

[Activity] Week #23

by Arthur She

# Progress # * [QA-714] * The patch had been merged * [QA-716] * Submitted the patch and waiting for review * [QA-715] * Due to run whole test program will take a very long time, try to run separated test cases by giving parameter (n32, n64, s32, s64). # Plan # * [QA-715] * [BUG-1296880]

10 years, 7 months

LTP version upgrade in test definitions

by Milosz Wasilewski

Hi, Currently test definitions use LTP released on Jan 15th 2014. New version of LTP was released Apr 22nd 2014. I'm planning to switch Linaro test definitions to this version on Monday. If there are any objections please shout now. Best Regards milosz

10 years, 7 months

[Activity] Week #23

by Neil Williams

# Progress # * LAVA-333 * merged packaging branch into master * marked lava-manifest and lava-deployment-tool dev mode as end of life * planning the downtime for migration of production. * running tests on migrated staging.validation.linaro.org * Time * packaging: 10% * migration: 90% -- Neil Williams ============= http://www.linux.codehelp.co.uk/

10 years, 7 months

lava-deployment-tool end of life - remove local buildouts before upgrading

by Neil Williams

LAVA is migrating to packaging for installation and upgrades. There have already been notices posted about the migration and the availability of packages and package updates on this list. http://staging.validation.linaro.org and http://playground.validation.linaro.org have already been migrated. The time has come to merge the packaging support into the master git branch and this has known consequences for installations using lava-deployment-tool. lava-deployment-tool production installs remain supported until validation.linaro.org is migrated to packaging during a scheduled downtime window which is likely to be at the end of this month (June 2014). lava-manifest will be end-of-life at the same time. lava-deployment-tool *developer mode* is end-of-life today. lava-manifest is being updated to stop upgrading passed versions at the last supportable commits for developer mode. Once validation.linaro.org is migrated, all lava-deployment-tool instances will be stopped from upgrading beyond the last commit prior to the merge. There are particular concerns with developer mode and local buildouts: Any buildout based on upstream LAVA git repositories (or rebased to pull in upstream LAVA git) *will* break the existing LAVA instance. This is unavoidable and entirely predictable - lava-deployment-tool is unable to migrate LAVA from django1.4 to django1.6 and there is no lava-deployment-tool support for LAVA development beyond this point. Please remove all local buildouts from lava-deployment-tool instances and do *not* update or rebase the buildout to latest LAVA git master after today. lava-deployment-tool is gaining a check to fail any upgrade where local buildouts exist, until those buildouts are removed. Developer mode instances using lava-deployment-tool will get no further code updates. There is no need to actually migrate from developer mode back to production mode, the necessary migration is to packaging. Production mode instances using lava-deployment-tool will only get hot fixes via the release branch until the migration of validation.linaro.org. At that point, the master branch will be merged into release and this will mark the formal end of support for lava-deployment-tool. Please take time to read the migration notes and to decide on how your lava-deployment-tool instances should be upgraded. https://staging.validation.linaro.org/static/docs/migration.html Once upgraded, tools are provided to build updated packages based on local code as well as binary packages being uploaded to Debian (then migrating into Ubuntu Unicorn). There are two options currently: Debian Jessie (testing) - the recommended upgrade as this is the path which the LAVA team will follow. staging and playground are already running this install. Development in LAVA is now based on Debian. Latest updates are based on Debian unstable and changes are migrated into Jessie (current testing) intermittently. staging is already running Jessie with packages updated based on unstable. Ubuntu Trusty Tahr 14.04LTS - A lot of LAVA dependencies were not included into Trusty, so unlike Jessie, users who choose Trusty are recommended to consider upgrading to Unicorn which will receive updates of these dependencies via Debian. More information and detailed guides on how to migrate are available in the migration documentation on staging. https://staging.validation.linaro.org/static/docs/migration.html -- Neil Williams ============= http://www.linux.codehelp.co.uk/

10 years, 7 months

More attempts to deploy to mustang in LAVA

by Michael Hudson-Doyle

Hi, I'm still trying to deploy to the disk of a mustang in the LAVA lab (without rewriting the dispatcher). I have something that looks like it should work: https://github.com/mwhudson/lava-deploy-job/blob/master/job.json It dd's an Ubuntu cloud image (just a raw image made out of the ubuntu-provided qcow) onto /dev/sda, reboots and tries to run flash kernel to render it bootable. This isn't quite going to work for a couple of reasons, but the failure is confusing to me: https://validation.linaro.org/scheduler/job/130989/log_file Why doesn't the device reboot between the steps? (I'm also not sure why the networking fails when chrooted but that's separate I think). CHeers, mwh

10 years, 7 months

LavaServer - adding a new device

by Chisanovici, IonutX

Hi, I'm new/beginner with lava. I recently installed a lava server on one Ububtu 12.04 machine. I'm planning the use the lava server to see the duration time of some "builds" that will be performed on another Fedora 20 desktop machine. My question is: is there any way to add the Fedora 20 machine as a device in the lava server and then to setup a bundle stream ? If yes, how can I do it ? Thank you, Ionut C

10 years, 7 months

Package update for 2014.05 tag

by Neil Williams

10 years, 7 months

[Activity] Week #22

by Senthil Kumaran

# Progress # * LAVA-1192 Archive LAVA log files older than a time limit * LAVA-1320 Archive root directory * LAVA-1321 Adjust UI to show job file is archived * LAVA-1344 Archive script recommended by LAVA * various code reviews * Time * Cards - 15% * various code reviews - 5% # Plan # * pending LAVA cards * bug fixes -- Senthil Kumaran http://www.stylesen.org/ http://www.sasenthilkumaran.com/

10 years, 7 months

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

linaro-validation June 2014