On 30 March 2014 02:31, Martin Jansa <martin.ja...@gmail.com> wrote: > There are always 20+ failed tasks in those > big builds and just reading the numbers isn't good indicator of quality, > because sooner you break something in dependency tree, fewer recipes will > be actually tested, so fewer failed tasks often means that something > important is broken. >
Sorry to double reply but had a thought on this one thing in particular. Is there any way to list recipes (or tasks) which weren't executed because a dependency failed? I know we see this at the start of the build if dependencies can't be satisfied, I'm thinking tasks with satisfied dependencies but then those dependencies fail. Being able to see that chain for each build may help us prioritise. It would also show whether a failure disappearing was due to the issue being fixed or the recipe no longer being attempted due to a new failure somewhere else. Thanks, -- Paul Barker Email: p...@paulbarker.me.uk http://www.paulbarker.me.uk -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
