У сре, 12. 12 2012. у 12:18 +0000, Matthew Gretton-Dann пише: > > What is the intention here? Are we going to have Lava be the > high-level builder, and so its 'tests' are each of the build steps, > and then the testsuite analysis is done elsewhere?
Yes, in this (first) phase, LAVA is only supposed to be used as a "native builder farm". Any LAVA specifics should, for now, be considered implementation details: i.e. a build happens just like before and cbuild collects the results and you look at them there. LAVA does give us access to some lower level details there, but we are not using it for what it was originally designed to do. The effort happening here doesn't tie in (directly) with Michael Hope's departure: it was planned a while ago to move from static board allocation to using the dynamic board allocation provided by LAVA. Next steps in that vision are to migrate cross-builds to jenkins (i.e. move all the builds to our shared infrastructure), and then integrate all the useful features of cbuild into our existing CI systems. For now, we'll also simply run the gcc testsuite as part of the build, just like it was done so far (as far as I understand it). We want to get to the goal (of TCWG using the common CI/validation infrastructure) step by step. Cheers, Danilo _______________________________________________ linaro-validation mailing list [email protected] http://lists.linaro.org/mailman/listinfo/linaro-validation
