[OE-core] [PATCH] ltp: update to 20140828 release

[Fathi Boudra]

On 4 November 2014 17:54, Richard Purdie <richard.purdie at linuxfoundation.org
> wrote:

> On Tue, 2014-11-04 at 17:10 +0200, Fathi Boudra wrote:
> > after a lot of finger-pointing and implying we don't test our changes
> > or do our homework or do clean builds:
> > * I've built ltp for armv7a and armv8 on our builders and it works
> > fine
> > * I've built poky for x86 and it built fine
> >
> > here's my steps:
> > $ git clone git://git.yoctoproject.org/poky
> > $ cd poky
> > $ source oe-init-build-env
> > $ patch -p1 < 0001-ltp-update-to-20140828-release.patch
> > $ bitbake ltp
> >
> > $ ls -l tmp/deploy/rpm/i586/ltp-*
> > -rw-r--r-- 2 user user 55929600 Nov  4 16:28
> > tmp/deploy/rpm/i586/ltp-20140828-r0.i586.rpm
> > -rw-r--r-- 2 user user     3080 Nov  4 16:28
> > tmp/deploy/rpm/i586/ltp-dbg-20140828-r0.i586.rpm
> > -rw-r--r-- 2 user user     3264 Nov  4 16:28
> > tmp/deploy/rpm/i586/ltp-dev-20140828-r0.i586.rpm
> > -rw-r--r-- 2 user user    31884 Nov  4 16:28
> > tmp/deploy/rpm/i586/ltp-doc-20140828-r0.i586.rpm
> >
> > afaict, the failure isn't related to the changes submitted. Could you
> > be kind enough to try to reproduce the build failure outside of the
> > yocto autobuilders? or give me the exact steps to reproduce the
> > failure?
>
> bitbake libtirpc; bitbake ltp
>

It explains... the issue is triggered only if libtirpc is built before ltp.
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.

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.


>
> seems to reliably reproduce for me.
>

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...


>
> Cheers,
>
> Richard
>
>
>
Cheers,
Fathi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20141105/88760579/attachment-0002.html>