On Fri, Mar 11, 2016 at 11:13 AM, Martin Jansa <martin.ja...@gmail.com> wrote:
> On Fri, Mar 11, 2016 at 10:52:14AM -0500, Bruce Ashfield wrote: > > On Fri, Mar 11, 2016 at 10:41 AM, Mark Hatle <mark.ha...@windriver.com> > > wrote: > > > > > On 3/10/16 5:53 AM, Martin Jansa wrote: > > > > Aggressive PNBLACKLISTing continues. But linux-yocto (and modules > > > depending on it) > > > > are still broken :/. > > > > > > > > I'll look at cef3 and chromium issue, my recent patch for > meta-browser > > > > fixed the build for armv7a MACHINEs, so it probably needs to be > extended > > > > a bit to cover warnings in x86 and then duplicate the same to cef3. > > > > This issue is there for so long, slowing down the builds > significantly > > > > (and causing logs to be much bigger) - I don't use these recipes but > I > > > > hate the failures even more. > > > > > > > > > > Is see the reported log failure, but I've been building with the > oe-core > > > and > > > poky linux-yocto head of master for the last couple weeks, all arches > > > includes > > > qemux86. > > > > > > > > > I don't know what to say about those failures either. I've been chasing > > perf build > > races for the past week, and that includes building linux-yocto hundreds > of > > times, > > and I've never seen the uapi headers not be in place like the logs show. > > My guess (and supported by Andrea) is that it's caused by > linux-yocto-tiny which is built as part of bitbake world and probably > not included in your tests when you build the same linux-yocto. > > Aha. Thanks, I'm working those problems as well and did reproduce a variant when rm_work is enabled. So I do have a thread to tug on for the failure. With that, plus your description below, I've got a better chance of seeing it. Cheers, Bruce > That would also explain why these issues break almost every qemux86 and > I haven't seen them for qemuarm, linux-yocto-tiny has: > COMPATIBLE_MACHINE = "(qemux86)" > > Try to run > "bitbake linux-yocto linux-yocto-tiny" couple times and maybe you'll be > able to reproduce it. > > For next runs I've PNBLACKLISTED linux-yocto-tiny and > linux-yocto-tiny-kexecboot: > > https://github.com/shr-project/jenkins-jobs/commit/c168b7824c2c68bd5894532fc122929d2d9df9a7 > > > The Yocto AB is also not showing it to me. > > > > Unless I can get access to a broken build, I'm at a loss to actually > debug > > and > > fix it. > > > > Bruce > > > > > > > > > > I don't see the error on my builder. Is something changing the default > > > recipe/kernel configuration triggering the fault? > > > > > > --Mark > > > > > > > === qemux86 (2) === > > > > * /meta-openembedded/meta-python/recipes-devtools/python/ > > > python-m2crypto_0.23.0.bb, do_compile > > > > * /openembedded-core/meta/recipes-kernel/linux/ > linux-yocto_4.4.bb, > > > do_compile > > > > > > > > > -- > > > _______________________________________________ > > > Openembedded-core mailing list > > > openembedded-c...@lists.openembedded.org > > > http://lists.openembedded.org/mailman/listinfo/openembedded-core > > > > > > > > > > > -- > > "Thou shalt not follow the NULL pointer, for chaos and madness await thee > > at its end" > > -- > Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com > -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" -- _______________________________________________ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel