linaro-validation

linaro-validation@lists.linaro.org

818 discussions

by Marco Felsch

Dear Linaro Developer, First of all you made a very great validation system *thumbs up* I had set up a LAVA instance 2 weeks ago and all works well. But there are a few questions. 1. I use the “deploy_kernel” options, but with my own kernel,dtb and rootfs (and my own prompt).It is possible to define the “prompt” in the “deploy_kernel”-section? 2. I had read a lot of stuff on the LAVA doc-site and on many presentations and I saw your Jenkins-LAVA setup. How do I configure the LAVA Server, that he triggers test-jobs after a successful Jenkins-build? Cheers, Marco

10 years, 2 months

Install LAVA on Ubuntu 12.04

by Zhongwei Yao

Hi, All, Does LAVA support Ubuntu 12.04? If yes, how can I install it? I haven't found related doc at: https://validation.linaro.org/static/docs/installation.html -- Best regards, Zhongwei

10 years, 2 months

LAVA image reports

by Zhongwei Yao

Hi, all. I'm looking at LAVA and try to use it on a benchmark system. I would like benchmark system's result show in a web page. I find LAVA have a "Image Reports" feature. But it seems only show pass or fail count in some examples, e.g. LAVA sample <https://validation.linaro.org/dashboard/image-reports/lava-master-installat…> . My question is: is LAVA able to show data like 233 ms from benchmark? Like this one: chart_example <https://chromeperf.appspot.com/report?masters=ChromiumPerf&bots=android-nex…> -- Best regards, Zhongwei

10 years, 2 months

Object has unknown property u'modules'

by Ciprian Barbu

Hi, What happened with the modules parameter? It used to be available and used to pass in the kernel modules to a job. Now I get this error: ValidationError: Object has unknown property u'modules' but additional properties are disallowed object_expr='object', schema_expr='schema.additionalProperties') /Ciprian

10 years, 2 months

Debian Jessie has a target release date - April 25th

by Neil Williams

Jessie Release ============== We now have a target release date of Saturday the 25th of April. We have checked with core teams, and this seems to be acceptable for everyone. This means we are able to begin the final preparations for a release of Debian 8 - "Jessie". The intention is only to lift the date if something really critical pops up that is not possible to handle as an errata, or if we end up technically unable to release that weekend. Please keep in mind that we intend to have a quiet period from Saturday the 18th of April. Bug fixes must be *in Jessie* before then. https://lists.debian.org/debian-devel-announce/2015/03/msg00016.html LAVA is in Jessie without any issues and releases after 2014.09 are in experimental. Shortly after 25th April, the version of LAVA in experimental at the time (or the pending production release, depending on timing) will be uploaded to unstable and subsequently migrate into the new Debian testing: Stretch. (Stretch is the purple octopus from Toy Story 2). Shortly after the release, stable-backports will become available. Once LAVA migrates into stretch, a backport can be made to stable-backports. So instances can stay on Debian 8.0 Jessie (stable) and remain up to date with production using stable-backports. Around the 18th April, Wheezy will become oldstable. There is no LAVA support in Wheezy. What you need to do now =================== Now is a good time to check the apt sources of *all* your Debian boxes, including VMs: $ cat /etc/apt/sources.list /etc/apt/sources.list.d/* example apt source using testing: deb [arch=arm64] http://mirror.bytemark.co.uk/debian/ testing main example apt source using jessie: deb [arch=arm64] http://mirror.bytemark.co.uk/debian/ jessie main For all boxes with apt sources pointing at official Debian mirrors, the following items need to be considered: 0: If your apt source is testing then the next upgrade after 25th April will move you to Stretch. You will receive updates to LAVA automatically, typically after a 5 day migration delay from unstable. 1: If your apt source is jessie, then the next upgrade after the 25th will move you to stable and subsequently a point release of stable. You will need backports to stay up to date with LAVA. 2: IMPORTANT: The first few weeks after a stable release can be *chaotic* in the unstable suite with so many new uploads - the release team try to protect the testing suite in this case, stretch, but some breakage can be expected, even in testing (stretch). The way to manage this is to be sensible about *which* boxes you upgrade during this time. 3: It is common for a stable release to be quickly followed by a point release, this isn't scheduled yet but is likely to be between the release and DebConf15 in August, most probably some time in June or July. LAVA is not likely to be a candidate for a point release update, updates will continue via stable-backports. 4: If you have both testing and jessie in your apt sources on a single machine, then unless you are also using manually configured apt pinning, that box will upgrade using the testing source and move to stretch as per point 0. Backports of LAVA will start to become available for jessie via stable-backports shortly after LAVA packages migrate into stretch for the first time. There will be an inevitable delay of as much as 10 days between a production release and that release arriving in stable-backports. For LAVA lab boxes, there will continue to be the images.validation.linaro.org/production-repo which will allow those boxes to stay on jessie without the delay in waiting for backports. This is how validation.linaro.org will be updated. So, consider each of your boxes and decide *now* how these are to migrate. Changing between testing and jessie now is safe - which one is in place after 25th April 2015 is what matters. More details of configuring stable-backports will be available once stable-backports is open for uploads. For now, look at backports.debian.org A new install of Debian 8.0 Jessie after 25th April will use an apt source of jessie and will behave in the same manner as per point 1, typically adding stable-backports support as well. The LAVA team expect to support jessie via backports for the lifetime of jessie as stable - once stretch gets to a point where a release freeze is being considered (probably around summer next year, 2016) we'll look at whether jessie can continue to be supported as "oldstable" into 2017. -- Neil Williams ============= neil.williams(a)linaro.org http://www.linux.codehelp.co.uk/

10 years, 3 months

Re: [Linaro-validation] Lava Job submission running issue.

by Senthil Kumaran

On Thursday 26 February 2015 05:23 PM, Narendra Kumar wrote: > For panda-board we need to have empty sd card(with out any > partitioning) for deploying image using json file, currently I am using > telnet to connect to board so apart from connectin_command do we need to > specify any more command related to image installation and boot commands? You can see the panda device configuration used in v.l.o here - https://git.linaro.org/lava/lava-lab.git/blob/14f6fbacafe1819c8a0c51e9f2603… For panda-es boards the configuration is here - https://git.linaro.org/lava/lava-lab.git/blob/14f6fbacafe1819c8a0c51e9f2603… Based on your board type ie., panda-es or panda, choose either of the configuration as reference. PS: Keeping LAVA mailing list in CC. Thank You. > On Wed, Feb 25, 2015 at 6:30 PM, Senthil Kumaran > <senthil.kumaran(a)linaro.org <mailto:senthil.kumaran@linaro.org>> wrote: > > On Wednesday 25 February 2015 06:27 PM, Narendra Kumar wrote: > > I have changed the LAVA_SERVER_IP in lava-dispatcher.conf now it started > > working, I hope there won't be any more issues. Once it successfully > > finished I will let you know. Thank you very much for quick response. > > Great to know that! > > Thank You. > -- > Senthil Kumaran > http://www.stylesen.org/ > http://www.sasenthilkumaran.com/ > > > > > -- > tree pinePlease consider the environment before printing this e-mail > > Thanks & Regards > Narendra Kumar Chepuri > (+917353049544) -- Senthil Kumaran http://www.stylesen.org/ http://www.sasenthilkumaran.com/

10 years, 3 months

Lava Job submission running issue.

by Narendra Kumar

Hi, I wants to run lava for testing the image on panda-board, for that I have followed steps mentioned in https://www.youtube.com/watch?v=T8jFzXRrFh8&feature=youtu.be but till job submission everything is fine but after job submission we need to click on the job_id and we need to refresh the page so the test will start its execution on board but I have refreshed many time test has not started, can any one tell any steps are missed while adding or before adding the device for accessing the device by lava-server? I am sharing the files which I used for test trigger. Note:command "lava connect 4000(port to which panda board is connected)" is working properly and I am able to connect to boards terminal. -- [image: tree pine]Please consider the environment before printing this e-mail Thanks & Regards Narendra Kumar Chepuri (+917353049544)

10 years, 4 months

Re: [Linaro-validation] Lava set up in ubuntu 14.10 utopic unicorn

by YongQin Liu

I think the validation mailing list is the right place for you question. On 19 February 2015 at 20:12, Narendra Kumar < narendrakumar.chepuri(a)gmail.com> wrote: > Hi, > > Sorry for disturbing you. > > This question I might have several times in free-node channel, I > got a suggestion to follow you-tube I will not comment on those videos but > still those videos are not enough for new user like me to setup lava. any > way I am able to install lava local host, Only help I need is how to start > lava for running some tests on devices like panda board. I want to run ltp > on panda using lava-test-shell, please consider my mail, its very important > and I am critical condition now(stopped in middle to proceed further). As a > new user of lava I am not getting any thing in lava documentation part, > hope you understand the situation. > > > Note:: Please don't share linaro documentation links as a reply. > > -- > [image: tree pine]Please consider the environment before printing this > e-mail > > Thanks & Regards > Narendra Kumar Chepuri > (+917353049544) > > _______________________________________________ > linaro-android mailing list > linaro-android(a)lists.linaro.org > http://lists.linaro.org/mailman/listinfo/linaro-android > > -- Best Regards, Yongqin Liu --------------------------------------------------------------- #mailing list linaro-android(a)lists.linaro.org <linaro-dev(a)lists.linaro.org> http://lists.linaro.org/mailman/listinfo/linaro-android

10 years, 4 months

Changes to lava-team hacking session code

by Neil Williams

https://review.linaro.org/#/c/4662/ has been merged into https://git.linaro.org/lava-team/hacking-session.git https://git.linaro.org/lava-team/hacking-session.git/commit/2c58c1e43965550… This change was the result of a talk at HKG15 about abandoned hacking sessions. The changes can be summarised as: * If user doesn't log in to hacking session within 60 minutes, the session is terminated. * default behavior is changed and the session is terminated upon logging out. * When user would like to continue hacking session the 'continue_hacking' command is provided. * Android multinode hacking session was fixed and it closes both nodes properly. Example jobs using the new code: https://staging.validation.linaro.org/scheduler/job/119912/log_file https://staging.validation.linaro.org/scheduler/job/119911 Note the new code produces useful test results from the hacking session: https://staging.validation.linaro.org/dashboard/streams/anonymous/codehelp/… Thanks to Milosz for implementing the changes from the session. -- Neil Williams ============= neil.williams(a)linaro.org http://www.linux.codehelp.co.uk/

10 years, 4 months

About the units display in the result bundle page

by YongQin Liu

Hi, All I have a test that without units generated before. now I added the units part for the test result. >From the output here, the parsing of the result should be right: https://validation.linaro.org/scheduler/job/257061/log_file#L_9 but the units information are not shown in the result bundle page: https://validation.linaro.org/dashboard/streams/private/team/wg/wg-private/… Anyone can help to check what's the problem there? If it is because that the tests before does not have unit information, please tell me how to make the unit information displayed now? Thanks in advance! -- Best Regards, Yongqin Liu --------------------------------------------------------------- #mailing list linaro-android(a)lists.linaro.org <linaro-dev(a)lists.linaro.org> http://lists.linaro.org/mailman/listinfo/linaro-android

10 years, 4 months

← Newer
1
...
6
7
8
9
10
11
12
...
82
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

linaro-validation