On 12 June 2012 12:48, Alexander Sack asac@linaro.org wrote:
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
What do you mean. The kernel is built as part of the platform, like it is today.
In general I agree though that sticking to the pristine upstream instructions is a worthwhile goal.
I think you misunderstood. All I want to do is to allow people to build Android using the instructions listed on android.com. These would be:
source build/envsetup.sh lunch full_panda-eng
instead of:
wget --no-check-certificate http://android-build.linaro.org/download/linaro-android_toolchain-4.7-bzr/la...
tar -jxvf android-toolchain-eabi-linaro-*
export NUM_PROC=`getconf _NPROCESSORS_ONLN`
make -j${NUM_PROC} HOST_CC=gcc-4.7 HOST_CPP=cpp-4.7 HOST_CXX=g++-4.7 TARGET_PRODUCT=pandaboard TARGET_SIMULATOR=false TARGET_TOOLS_PREFIX=/path/to/toolchain/arm-linux-androideabi- boottarball systemtarball userdatatarball showcommands > build_log_YYMMDD.txt 2>&1 &
...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.
I think this is way easier. When LAVA runs the test it just kicks off well named script and the script takes it from there.
So first: is there such a solution for AOSP already? Do they have a generic way to invoke "AOSP" tests by name?
Yeah, you send intents to them on the command line via adb.
If not, can we get a smart magic build system patch that produces such a test manifest?
I don't think we need a seperate test manifest. We just need a set of test gits that we include in the single manifest. Then things are all in one place.
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?
Well you can just send an intent on the command line to a test entry point. You could wrap this with a little script.
-- Alexander Sack Technical Director, Linaro Platform Teams http://www.linaro.org | Open source software for ARM SoCs http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog