<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 4 November 2014 17:54, 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"><div class="HOEnZb"><div class="h5">On Tue, 2014-11-04 at 17:10 +0200, Fathi Boudra wrote:<br>
> after a lot of finger-pointing and implying we don't test our changes<br>
> or do our homework or do clean builds:<br>
> * I've built ltp for armv7a and armv8 on our builders and it works<br>
> fine<br>
> * I've built poky for x86 and it built fine<br>
><br>
> here's my steps:<br>
> $ git clone git://<a href="http://git.yoctoproject.org/poky" target="_blank">git.yoctoproject.org/poky</a><br>
> $ cd poky<br>
> $ source oe-init-build-env<br>
> $ patch -p1 < 0001-ltp-update-to-20140828-release.patch<br>
> $ bitbake ltp<br>
><br>
> $ ls -l tmp/deploy/rpm/i586/ltp-*<br>
> -rw-r--r-- 2 user user 55929600 Nov 4 16:28<br>
> tmp/deploy/rpm/i586/ltp-20140828-r0.i586.rpm<br>
> -rw-r--r-- 2 user user 3080 Nov 4 16:28<br>
> tmp/deploy/rpm/i586/ltp-dbg-20140828-r0.i586.rpm<br>
> -rw-r--r-- 2 user user 3264 Nov 4 16:28<br>
> tmp/deploy/rpm/i586/ltp-dev-20140828-r0.i586.rpm<br>
> -rw-r--r-- 2 user user 31884 Nov 4 16:28<br>
> tmp/deploy/rpm/i586/ltp-doc-20140828-r0.i586.rpm<br>
><br>
> afaict, the failure isn't related to the changes submitted. Could you<br>
> be kind enough to try to reproduce the build failure outside of the<br>
> yocto autobuilders? or give me the exact steps to reproduce the<br>
> failure?<br>
<br>
</div></div>bitbake libtirpc; bitbake ltp<br></blockquote><div><br></div><div>It explains... the issue is triggered only if libtirpc is built before ltp.</div><div>It isn't the case when, on a clean build, you do only bitbake ltp or even when you build core-image-minimal before ltp, without mentioning our builders don't pull libtirpc either.</div><div><br></div><div>Patch v2 on its way. libtirpc wasn't detected until this latest release, hence network/rpc test cases haven't been built until now and they are broken upstream. Until, it's fixed upstream, I added a knob to disable tirpc on configure like it's already done for numa. Fixing properly the issue upstream might take a bit longer unfortunately.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
seems to reliably reproduce for me.<br></blockquote><div><br></div><div>yes, in a particular configuration so I don't think we deserved your rant from last week. Obviously, we've done the testing that would have been expected from us. It's nice that the autobuilders caught this issue but from a developer point of view, I don't build world but only the recipe modified and that's a problem to not have a deterministic chain of build dependencies when you use different configurations...</div><div> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Cheers,<br>
<br>
Richard<br>
<br>
<br>
</blockquote></div><br clear="all"><div>Cheers,</div><div>Fathi</div>
</div></div>