On Sat, Feb 11, 2017 at 10:55 AM, Aníbal Limón <anibal.li...@linux.intel.com > wrote:
> During the development of this script based on OEQA framework i found a > bug causing don't display stack traces, i sent a fix to the ML [1] also > is on my branch at [2]. > > I attached and example of how a log file looks, the example log results > are based on meta-yocto-bsp. > > Cheers, > alimon > > [1] > http://lists.openembedded.org/pipermail/openembedded-core/ > 2017-February/132494.html > [2] > http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/ > log/?h=alimon/yp_compatible > This seems like a good start, but this isn’t useful: AssertionError: True is not false : Layer meta-yocto-bsp changed signatures. Presumably this is telling the user it’s modifying things without using the appropriate overrides for machine or distro, but it doesn’t actually tell them that, and displaying the changed checksums isn’t of a great deal of use on its own either, I’d suggest at least capturing the changed variables via bitbake-diffsigs or bitbake -S printdiff. -- Christopher Larson kergoth at gmail dot com Founder - BitBake, OpenEmbedded, OpenZaurus Senior Software Engineer, Mentor Graphics
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
