On Tue, 06 Sep 2011 13:24:49 -0000
Alexander Sack <email address hidden> wrote:
> On Tue, Sep 6, 2011 at 2:24 PM, Frans Gifford
> <email address hidden>wrote:
>
> > Feel free to mark as invalid if you think this is the correct
> > behaviour.
> >
> >
> maybe a third state: SUCCESSWITHPROBLEMS would be another option? Not
> sure how easy that is to do on jenkins. I guess this stuff ultimately
> needs to be visualized on a lava dashboard with info like: build,
> lava submission, boot, tests etc. in one shot.
Actually, Jenkins exactly has those standard states: success, build
failed (failure), build succeeded, but tests failed (unstable). It's
just we don't use Jenkins right, so not clear how easy it would be to
do that quickly.
On Tue, 06 Sep 2011 13:24:49 -0000
Alexander Sack <email address hidden> wrote:
> On Tue, Sep 6, 2011 at 2:24 PM, Frans Gifford
> <email address hidden>wrote:
>
> > Feel free to mark as invalid if you think this is the correct
> > behaviour.
> >
> >
> maybe a third state: SUCCESSWITHPROBLEMS would be another option? Not
> sure how easy that is to do on jenkins. I guess this stuff ultimately
> needs to be visualized on a lava dashboard with info like: build,
> lava submission, boot, tests etc. in one shot.
Actually, Jenkins exactly has those standard states: success, build
failed (failure), build succeeded, but tests failed (unstable). It's
just we don't use Jenkins right, so not clear how easy it would be to
do that quickly.
>
> --
>
> - Alexander
>
--
Best Regards,
Paul
Linaro.org | Open source software for ARM SoCs www.facebook. com/pages/ Linaro twitter. com/#!/ linaroorg - http:// www.linaro. org/linaro- blog
Follow Linaro: http://
http://