On Sun, Apr 1, 2012 at 3:51 AM, Andy Doan <[email protected]> wrote: > On 3/31/12 6:43 AM, Alexander Sack wrote: >> >> May I propose to a list of the files we patch/touch and coordinate >> with Zach so he can remember to coordinate with LAVA team such a >> change? >> >> In this way we can avoid LAVA team finding out about this through job >> bustage :). > > > I'm a +1 for this and saw Paul's response from the technical standpoint. > However, I think we also need to take a step back and ask why it took _me_ > to identify this was happening. > > I only uncovered this because I couldn't get my benchmark jobs to execute. > The panda tracking build has been broken since build 229 (8 days ago) and > all of the 12.03 builds failed to actually run in LAVA. > > In other words, are we really submitting LAVA jobs and not caring about the > results? >
Thats the case, yes. The point is that the general flakyness makes it hard to establish folks being hard about getting no green on LAVA... so chicken, egg. -- Alexander Sack Technical Director, Linaro Platform Teams http://www.linaro.org | Open source software for ARM SoCs http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog _______________________________________________ linaro-validation mailing list [email protected] http://lists.linaro.org/mailman/listinfo/linaro-validation
