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/
Hi,
I've just made a fresh Debian (Jessie) installation.
Then, I've added jessie-backports and installed lava-server from there.
Once the installation completed, I've rebooted and the GUI desktop
environment doesn't come up.
This happened twice already, so it's definitely the Lava installation
that's breaking something there. Is this a known issue? Any suggestions?
Regards,
matallui
Hi,
I had a boot issue and it was because of using SPACE to stop the autoboot. A quick fix for this was to add a \" to a variable declaration such as "setenv dummy variable\"". Do you know of any other fix for this? It seems the default for lava is "Hit any key to stop autoboot" and just send a "b" to stop it. In my case, I had to change the device configuration file to look for "Press SPACE to abort autoboot in 2 seconds" and then send a " ". The device configuration looks as follows http://pastebin.ubuntu.com/18790420/.
Now I have another issue where the job keeps going even though the image booted successfully. I want it to stop once it sees "am335x-evm login:". Is there a way to do this? I changed the master_str = am335x-evm login:.
This is my complete log http://pastebin.ubuntu.com/18790288/.
Thanks,
Josue
Dear Lava team,
We're deploying Lava V2. So far we've been working on old servers to prototype our installation. We're now almost ready to order our definitive PCs.
We have assessed some key features for our Lava server. Still, we're not 100% sure on how powerful it should be.
Is it possible for you to share the main characteristics of your current Lava servers (Number of cores, RAM, size of disk)? That would be helpful.
Thanks and best regards,
Denis Humeau
Hi,
I'm currently trying to configure a Switched Rack PDU to the lava instance.
How do I know if the driver for my PDU APC AP7901 is supported in the framework?
I got it connected both via serial and telnet. My /etc/lavapdu/lavapdu.conf file is attached.
Also, when I restart the lavapdu-runner it fails with the error that is attached.
As for the beaglebone black support, I have a device dictionary but where should I save it so lava can access it? I've seen that the pdu hostname is always similar to pdu05. How do I know my pdu's hostname?
I appreciate the help, thanks.
Regards,
Josue Albarran