On 22 August 2012 15:36, Michael Hudson-Doyle <[email protected]> wrote: > Andy Doan <[email protected]> writes: > >> On 08/21/2012 07:48 AM, Dave Pigott wrote: >>> On 21 Aug 2012, at 12:16, Alexander Sack wrote: >>>> On this front: is there an easy way to check that a certain build >>>> is suitable for health check? If so, we could make that part of >>>> our monthly validation process and daily dashboard and assign >>>> priority to bugs that would disqualify a build from being suitable >>>> as a health check... >>>> >>>> What do you think? >>> >>> Hmm. Nice idea, and I was thinking along similar lines as we were >>> going through this crisis. We need to think about this and how we >>> might achieve it. >> >> I had my 1x1 with asac and have a thought on this. Lets take the monthly >> releases and submit like 50 jobs for that image that work like a health >> job. We can then look at the results and see how it compares to the >> previous month's releases. This should help us know what's good and also >> provide some valuable metrics to the other Platform teams in Linaro. > > That said, I don't really see why we'd change which image our health > check board uses unless we had a good reason. The point of them is to > keep an eye on the state of the hardware...
If its all the same I think we should shut off beagle and stick with Panda. Running beagle when we don't need too has other costs. > > Cheers, > mwh > > _______________________________________________ > linaro-android mailing list > [email protected] > http://lists.linaro.org/mailman/listinfo/linaro-android -- Zach Pfeffer Android Platform Team Lead, Linaro Platform Teams Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog _______________________________________________ linaro-validation mailing list [email protected] http://lists.linaro.org/mailman/listinfo/linaro-validation
