On 4 December 2012 17:17, Alexander Sack <alexander.sack@linaro.org> wrote:

thanks Soumya... keep on notifying us about these things please :)

Next time include the build team that is doing the builds as they are
usually the folks breaking stuff and should drive the resolution once
its known (CCed public android list now)

The initial Boot failures in LAVA were due to 4.2 upgrade where the partition mounting was updated. The issue was tracked here :

https://bugs.launchpad.net/lava-dispatcher/+bug/1084420

Currently the builds are broken due to infrastructure issues which is being resolved.

On Tue, Dec 4, 2012 at 12:39 PM, Soumya Basak <soumya.basak@linaro.org> wrote:
> Hi Andy,
> would you please have a look at our Daily Dashboard page,
>
> http://validation.linaro.org/lava-server/dashboard/image-reports/panda-jb-gcc47-tilt-tracking-blob
> http://validation.linaro.org/lava-server/dashboard/image-reports/snowball-jb-gcc47-igloo-stable-blob
> http://validation.linaro.org/lava-server/dashboard/image-reports/snowball-jb-gcc47-igloo-stable-blob
>
> Image report is stooped since 30 November 2012. also the boot test failure
> from last few builds.
> would you please update the issue, for our weekly test cases.
>
> Thanks
> Soumya Basak.
>

_______________________________________________
linaro-android mailing list
linaro-android@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-android