On Sat, Mar 31, 2012 at 8:51 PM, Andy Doan <andy.doan@linaro.org> 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?

That's how it would appear. My assumption has been that those jobs coming from the android ci system are looked at when the android team makes releases. One of the things I'm looking to do on the QA team is to start looking at manual and automated tests together, while starting to transition some of the manual tests to run in lava instead.

LAVA is quite capable of catching things like this, but someone has to care for the results and notice the breakage to make it useful.

Thanks,
Paul Larson