On 31 March 2012 20:51, 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?
Since LAVA:
1. Can't reliably boot all the builds in all configurations 2. Doesn't use linaro-android-media-create (which we tell users to use) 3. Doesn't use the right bootloaders
We've always hand tested our builds to ensure they work. Until LAVA:
1. Can program a build in the same manner we tell users to 2. Doesn't assume anything about the target, like it even booting
We have to keep hand testing.
-andy