On Tue, Jun 12, 2012 at 7:39 PM, Zach Pfeffer zach.pfeffer@linaro.org wrote:
Team,
Here's the idea, we put the build configuration and anything else we need to build the build into the build. We fix the builds so that people can use the instructions listed on:
The only thing I am not sure about is that I still haven't seen an official instruction that would build a full platform - including the kernel... so whatever we do, we might have slightly deviated way of doing things as we produce a fully bootable system
In general I agree though that sticking to the pristine upstream instructions is a worthwhile goal.
...and we add all the tests that LAVA would call and all the results parsing to the builds.
I liked the idea of having the build produce a test manifest (e.g. a flat file with test names included) that is shipped inside or even outside the image. On top we would like to have a standard way to run tests by name. With that we could allow LAVA and developerse to run the same tests using the same tools.
So first: is there such a solution for AOSP already? Do they have a generic way to invoke "AOSP" tests by name?
If not, can we get a smart magic build system patch that produces such a test manifest?
Also, how hard is it to provide a simple host tool that would make it damn easy to run test XXX on a target connected?