Thanks Neil Williams.


I tried creating sample job, looks like job not successful. How to debug and where to look for debug logs?


"ps -ax|grep lava" results below:


  795 ?        S      0:00 /usr/bin/python /usr/bin/lava-slave --master tcp://localhost:5556 --socket-addr tcp://localhost:5555 --level=DEBUG
  796 ?        Sl     0:00 /usr/bin/python /usr/bin/lava-dispatcher-slave --master tcp://localhost:5556 --socket-addr tcp://localhost:5555 --level=DEBUG
  798 ?        S      0:00 /usr/bin/python /usr/bin/lava-coordinator --loglevel=DEBUG
  860 ?        S      0:00 /usr/bin/python /usr/bin/lava-master manage --instance-template=/etc/lava-server/{{filename}}.conf --instance=default dispatcher-master
  863 ?        S      0:00 /usr/bin/python /usr/bin/lava-daemon manage --instance-template=/etc/lava-server/{{filename}}.conf --instance=default scheduler --logfile /var/log/lava-server/lava-scheduler.log --loglevel=debug
  864 ?        Sl     0:03 /usr/bin/python /usr/bin/lava-server manage --instance-template=/etc/lava-server/{{filename}}.conf --instance=default dispatcher-master
  865 ?        Sl     0:03 /usr/bin/python /usr/bin/lava-server manage --instance-template=/etc/lava-server/{{filename}}.conf --instance=default scheduler --logfile /var/log/lava-server/lava-scheduler.log --loglevel=debug
 1116 ?        S      0:00 /usr/bin/python /usr/sbin/lavapdu-listen --loglevel=DEBUG
 1242 ?        Ss     0:00 postgres: lavaserver lavaserver ::1(37311) idle                                                                             
 1248 ?        Ss     0:00 postgres: lavaserver lavaserver ::1(37312) idle  



lava-master, lava-daemon, lava-server's dispatcher and scheduler processes are taking "instance-template" argument from "/etc/lava-server/{{filename}}.conf" . Looks like {{filename}} is not resolved, I might have missed some steps. Can you please help how to correct it ?


thanks,

uma..

From: Neil Williams <neil.williams@linaro.org>
Sent: Wednesday, July 20, 2016 1:22:42 PM
To: Umamaheswara Rao Lankoti
Cc: Lava Users Mailman list; senthil.kumaran@linaro.org
Subject: Re: [Lava-users] LAVA setup for continuous integration validation of Android builds
 
On 20 July 2016 at 06:37, Umamaheswara Rao Lankoti
<ulankoti@innominds.com> wrote:
> Hi Neil Williams,
>
>
> Thanks for the clarification. I used debian jessie-backports option and
> installed lava. lava-server and lava-dispatcher versions installed are
> 2016.6-1. Earlier I tried to install lava without backports option on Jessie
> and installed version based in 2014.
>
> Installation type selected is "Single Master Instance" installation. Does it
> support V2 features ? Do I need to selection installation type as "Pipeline"
> explicitly for V2 features ?

Pipeline V2 is part of 2016.6 (and all releases since 2016.2). See the
LAVA v2 section of the Help menu on your own instance for more
information.

>
>
> thanks,
>
> uma..
>
> ________________________________
> From: Neil Williams <neil.williams@linaro.org>
> Sent: Tuesday, July 19, 2016 11:49:35 PM
> To: Umamaheswara Rao Lankoti
> Cc: Lava Users Mailman list; senthil.kumaran@linaro.org
> Subject: Re: [Lava-users] LAVA setup for continuous integration validation
> of Android builds
>
> On 19 July 2016 at 18:54, Umamaheswara Rao Lankoti
> <ulankoti@innominds.com> wrote:
>> Thank you Senthil Kumaran.
>>
>>
>> Looks like Debian Jessie supports only LAVA v1, which is deprecated.
>>
>> Is LAVA v2 on Debian Sid suggested for production use ?
>
> 2016.6-2 in unstable and testing has also been backported to
> jessie-backports and is the same version as is running on the
> Cambridge LAVA production lab.
>
> Debian unstable itself is less useful for production use. Install
> Debian Jessie, add an apt source for jessie-backports and then install
> the LAVA packages from backports.
>
> https://staging.validation.linaro.org/static/docs/v2/installing_on_debian.html#installing-on-debian-jessie
>
>>
>>
>> thanks,
>>
>> uma..
>>
>> ________________________________
>> From: Senthil Kumaran S <senthil.kumaran@linaro.org>
>> Sent: Tuesday, July 19, 2016 7:03:28 PM
>> To: Umamaheswara Rao Lankoti; Lava Users Mailman list
>> Subject: Re: LAVA setup for continuous integration validation of Android
>> builds
>>
>> 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/
>>
>>
>> _______________________________________________
>> Lava-users mailing list
>> Lava-users@lists.linaro.org
>> https://lists.linaro.org/mailman/listinfo/lava-users
>>
>
>
>
> --
>
> Neil Williams
> =============
> neil.williams@linaro.org
> http://www.linux.codehelp.co.uk/



--

Neil Williams
=============
neil.williams@linaro.org
http://www.linux.codehelp.co.uk/