On Tuesday 14 February 2012 16:13:46 Barros Pena, Belen wrote: > I've finally managed to put something together on how to handle build > failure in Hob 1.2. > > The document is here: > > https://wiki.yoctoproject.org/wiki/File:Build-fail-flow-v1.0.pdf
Looking through this document and talking to Belen there are a couple of things worth noting: * There will be build failures resulting from user configuration errors (e.g. network connection is unavailable -> fetch fails, or perhaps the sanity checker catches this earlier); however I suspect for the majority of people using Hob an error indicates a bug or some host system incompatibility (which is probably a bug). In this case all we can do for the user if they aren't capable of fixing the problem themselves is to provide them with an easy way to report the issue. * We plan to investigate implementing a "kerneloops" style build failure reporting system for 1.3 (see bug #1562). Part of this is about having the backend infrastructure to manage submitted issues, but the other is to have an interface to submit them and that will involve extensions to Hob. However as this won't be done for 1.2, in the mean time it might be possible to provide some other way of submitting build errors; but the question is where should they go? I'm not sure we want to default to filing a bug report or sending an email to the mailing list, for example. * We will probably need to embark on an exercise of enumerating the errors that can be produced by the build system (BitBake and metadata), after which we can analyse if certain errors can be handled in a better way, if specific handling can be added to a frontend such as Hob for some errors, and even if we can extend the documentation to cover how to troubleshoot certain classes of errors. This is of course not a small undertaking as a "git grep" of "bb\.*error" and "bb\.*fatal" and even scarier "raise " demonstrates. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
