<div dir="ltr">I use tmpfs in most of my builds, so in most cases when I see the error from the build, tmpfs is already gone (purged by next build executed on the same sever).</div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 6, 2015 at 11:32 PM, Richard Purdie <span dir="ltr"><<a href="mailto:richard.purdie@linuxfoundation.org" target="_blank">richard.purdie@linuxfoundation.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Wed, 2015-05-06 at 13:46 -0400, Bruce Ashfield wrote:<br>
> On 2015-05-06 12:07 PM, Martin Jansa wrote:<br>
</span><span class="">> > I've used master-next week or two ago (mostly to test bluez4 and python3<br>
> > changes) and soon after that dropped all linux-yocto related changes<br>
> > from it assuming that it's indeed cause for the issues I'm seeing, but<br>
> > it's not and it's still failing with master as well (and my<br>
> > jenkins/world builds are just small portion of my builds executed<br>
> > elsewhere where I see similar issues).<br>
><br>
> Richard: How can we sort out the differences between the build<br>
> environment that Martin uses versus what the autobuilder is showing?<br>
><br>
> There's nothing particularly complex happening during that build,<br>
> it's a checkout and generation of a config.<br>
><br>
> I'm unable to reproduce any of the failures, and neither is the<br>
> autobuilder.<br>
<br>
</span>This is a tough one and I'm struggling a little. We could try looking at<br>
the tmp/stamps/qemux86-poky-linux/linux-yocto/* files (sigdata in<br>
particular) as well as<br>
tmp/work/qemux86-poky-linux/linux-yocto/*/temp/log.task_order<br>
<br>
Martin, would you be able to share the above somewhere? I'm hoping this<br>
would give us a clue as to what the difference is between the builds and<br>
allow us to reproduce the problem.<br>
<br>
Cheers,<br>
<br>
Richard<br>
<br>
<br>
</blockquote></div><br></div>