Hi
LAVA is good for doing some tests but every time I use it I wonder why it is so slow. So I looked more at problem.
Job which I started is going on pandaboard for 48 minutes already. So far it did nothing related with tests which I want to run. Instead if fetched some image, booted and started installing lot of Python packages...
This got me to idea - why not make *-lava variants of images which would have all packages needed by LAVA infrastructure preinstalled? It would take some minutes of Jenkins but less then LAVA one probably. Especially when bigger set of jobs is to be run.
Opinions?
On Wed, May 23, 2012 at 6:21 PM, Marcin Juszkiewicz marcin.juszkiewicz@linaro.org wrote:
Hi
LAVA is good for doing some tests but every time I use it I wonder why it is so slow. So I looked more at problem.
Job which I started is going on pandaboard for 48 minutes already. So far it did nothing related with tests which I want to run. Instead if fetched some image, booted and started installing lot of Python packages...
This got me to idea - why not make *-lava variants of images which would have all packages needed by LAVA infrastructure preinstalled? It would take some minutes of Jenkins but less then LAVA one probably. Especially when bigger set of jobs is to be run.
FWIW, we had considered to do something similar to make big.LITTLE testing more convenient. So, I guess this is indeed a worthwhile idea to explore.
Assuming we want to do this, would we really make a -lava variant? Why not include the tests in the LEB directly? Android already ships the tests in the image, so it wouldn't be something entirely new.
On Wed, May 23, 2012, Alexander Sack wrote:
Assuming we want to do this, would we really make a -lava variant? Why not include the tests in the LEB directly? Android already ships the tests in the image, so it wouldn't be something entirely new.
+1; the test helpers should just be installed by default; I don't think having separate -lava images is a good idea, it's a lot of maintenance and direct costs when we can do it directly in our main images for little overhead.
On Thu, May 24, 2012 at 2:26 PM, Loïc Minier loic.minier@linaro.org wrote:
On Wed, May 23, 2012, Alexander Sack wrote:
Assuming we want to do this, would we really make a -lava variant? Why not include the tests in the LEB directly? Android already ships the tests in the image, so it wouldn't be something entirely new.
+1; the test helpers should just be installed by default; I don't think having separate -lava images is a good idea, it's a lot of maintenance and direct costs when we can do it directly in our main images for little overhead.
Yeah I think one can even argue that this is in line with the LEB purpose of being a "demo" system. Some of the test helpers probably have some nice demo effects :).
Anything we miss here? I guess we wouldn't need to prevent installing lava tests in general ... just ensure that all our "main" tests are installed by default.
If noone sees a reason against it, let's start by adding the tests we recently identified as "daily" tests for Ubuntu LEBs to the seed and see what we get...
Marcin Juszkiewicz marcin.juszkiewicz@linaro.org writes:
Hi
LAVA is good for doing some tests but every time I use it I wonder why it is so slow. So I looked more at problem.
Job which I started is going on pandaboard for 48 minutes already. So far it did nothing related with tests which I want to run. Instead if fetched some image, booted and started installing lot of Python packages...
It's even worse on fast models...
This got me to idea - why not make *-lava variants of images which would have all packages needed by LAVA infrastructure preinstalled? It would take some minutes of Jenkins but less then LAVA one probably. Especially when bigger set of jobs is to be run.
Opinions?
This idea has certainly occurred to me too. As Alexander says, our android image effectively do this already. Another approach, as discussed recently, is to not install lava-test itself on the board. If all you had to do was copy a statically linked binary to the board for test installation, that would be much faster...
Cheers, mwh