so following up:

panda tip build succeeded and the android test results showed up as expected and all looks fine (manually eyeballed the serial.log and 0xbench results seem to show up nicely).

here where the results show up:
 - android results: http://validation.linaro.org/lava-server/dashboard/reports/android-runs/
 - panda result: http://validation.linaro.org/lava-server/dashboard/permalink/test-run/e843ef08-cb38-11e0-9729-68b599be548c/ (for build https://android-build.linaro.org/jenkins/job/linaro-android_panda/237/)

leb-panda succeeded build as well, I can also see that LAVA was run with it when going to the job (http://validation.linaro.org/lava-server/scheduler/job/599) but I cannot figure what happened after that. Is there any way to find out what happened to that job (maybe serial.log for a scheduler job?)?

 -
 


On Sat, Aug 20, 2011 at 8:47 AM, Bernhard Rosenkranzer <bernhard.rosenkranzer@linaro.org> wrote:
Hi,
the 11.08 Android toolchain RC is ready:

https://android-build.linaro.org/builds/~linaro-android/toolchain-4.6-2011.08/#build=6
https://android-build.linaro.org/jenkins/job/linaro-android_toolchain-4.6-2011.08/6/artifact/build/out/android-toolchain-eabi-linaro-4.6-2011.08-6-2011-08-19_20-41-31-linux-x86.tar.bz2

The good news is that this build has been tested and seems to work
fine for everything so far.
The bad news is that we did that by reverting the switch from the
arm-eabi to the arm-linux-androideabi target, losing support for
OpenMP and friends. My theory is that the combination of an
arm-linux-androideabi toolchain and the mess in the Android build
system that works around the toolchain not knowing anything about the
OS simply don't go well together. We should investigate this further
for the next release.

Other than that, this toolchain build seems to be ready for release.
Let me know if you run into any problems.

ttyl
bero



--

 - Alexander