QA Logs now on tinderbox

QA Logs now on tinderbox

[Andrea Adami]

Hi,

yesterday oestats was expanded and now the QA errors are logged.

Here a first bunch of QA:

These two are the most common:

evil hides inside the .pc, staging,
/staging/armeb-angstrom-linux-gnueabi/usr/lib/pkgconfig/pycairo.pc

evil hides inside the .pc, staging,
/staging/armeb-angstrom-linux-gnueabi/usr/lib/pkgconfig/ORBit-2.0.pc

########

non dev contains .so, gcc,
/work/armv5teb-angstrom-linux-gnueabi/gcc-4.2.4-r3/install/gcc/usr/lib/gcc/armeb-angstrom-linux-gnueabi/4.2.4/libgcc_s.so

non dev contains .so, lirc,
/work/akita-angstrom-linux-gnueabi/lirc-0.8.1+cvs20070307-r1/install/lirc/usr/lib/liblirc_client.so

non dev contains .so, klibc,
/work/c7x0-angstrom-linux-gnueabi/klibc-1.5-r9/install/klibc/lib/klibc.so

non dev contains .so, libpython2,
/work/armv5teb-angstrom-linux-gnueabi/python-2.5.2-ml10/install/libpython2/usr/lib/libpython2.5.so

non dev contains .so, db,
/work/avr32-angstrom-linux-uclibc/db-4.3.29-r10/install/db/usr/lib/libdb-4.so

non dev contains .so, smpeg,
/work/armv5te-angstrom-linux-gnueabi/smpeg-0.4.5+rsvn370-r0/install/smpeg/usr/lib/libsmpeg.so

non dev contains .so, librfid,
/work/i586-angstrom-linux/librfid-0.2.0+svnr2094-r0/install/librfid/usr/lib/librfid.so


non dev contains .so, ewl-engines,
/work/armv5te-angstrom-linux-gnueabi/ewl-2_0.5.2.042+svnr35984-r3/install/ewl-engines/usr/lib/ewl/engines/evas_software_x11.so
non dev contains .so, ewl-engines,
/work/armv5te-angstrom-linux-gnueabi/ewl-2_0.5.2.042+svnr35984-r3/install/ewl-engines/usr/lib/ewl/engines/x11.so
non dev contains .so, ewl-engines,
/work/armv5te-angstrom-linux-gnueabi/ewl-2_0.5.2.042+svnr35984-r3/install/ewl-engines/usr/lib/ewl/engines/evas.so
non dev contains .so, ewl-engines,
/work/armv5te-angstrom-linux-gnueabi/ewl-2_0.5.2.042+svnr35984-r3/install/ewl-engines/usr/lib/ewl/engines/evas_buffer.so
non dev contains .so, ewl-engines,
/work/armv5te-angstrom-linux-gnueabi/ewl-2_0.5.2.042+svnr35984-r3/install/ewl-engines/usr/lib/ewl/engines/evas_fb.so
non dev contains .so, ewl-engines,
/work/armv5te-angstrom-linux-gnueabi/ewl-2_0.5.2.042+svnr35984-r3/install/ewl-engines/usr/lib/ewl/engines/evas_xrender_x11.so
non dev contains .so, ewl-engines,
/work/armv5te-angstrom-linux-gnueabi/ewl-2_0.5.2.042+svnr35984-r3/install/ewl-engines/usr/lib/ewl/engines/evas_software_16_x11.so


Andrea

Re: QA Logs now on tinderbox

[Robert Schuster]

[-- Attachment #1: Type: text/plain, Size: 371 bytes --]

Hi,
is there a way to override this being reported as a problem in case of
these problems:

> non dev contains .so, gcc,
> /work/armv5teb-angstrom-linux-gnueabi/gcc-4.2.4-r3/install/gcc/usr/lib/gcc/armeb-angstrom-linux-gnueabi/4.2.4/libgcc_s.so

I ask because boost on purpose distributes lib*.so files and creates a
lot of binary packages.

Regards
Robert


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 268 bytes --]

Re: QA Logs now on tinderbox

[Koen Kooi]

Andrea Adami wrote:
> Hi,
>
> yesterday oestats was expanded and now the QA errors are logged.
>
> Here a first bunch of QA:
>
> These two are the most common:
>
> evil hides inside the .pc, staging,
> /staging/armeb-angstrom-linux-gnueabi/usr/lib/pkgconfig/pycairo.pc
>
> evil hides inside the .pc, staging,
> /staging/armeb-angstrom-linux-gnueabi/usr/lib/pkgconfig/ORBit-2.0.pc

While I applaud the fact that people are starting to take QA seriously, 
I must stress that the current logs are highly misleading to most people.

Take a look at http://tinderbox.openembedded.net/packages/libtool/

The QA log for libtool (on armeb) says:

evil hides inside the .pc, staging, 
/staging/armeb-angstrom-linux-gnueabi/usr/lib/pkgconfig/pycairo.pc
evil hides inside the .pc, staging, 
/staging/armeb-angstrom-linux-gnueabi/usr/lib/pkgconfig/ORBit-2.0.pc

Both of these aren't part of the libtool packages, but part of 
python-pycairo_1.4.0.bb and orbit2_2.14.12.bb respectively.

The staging QA checks inspect the *complete* staging area, not just the 
files the recipe put in there. Some people have already started moving 
recipes to non-working because they didn't bother to look what was 
causing the QA error, but only acted on the last QA log on their screen. 
"Libtool has errors in its QA log, so it must be broken" - Bzzzzt! WRONG!

So please take care when you inspect the QA logs, things aren't always 
what they seem.

regards,

Koen

Re: QA Logs now on tinderbox

[Andrea Adami]

>These two are the most common:

Well, it is clear to me these are 'cruft' in staging. Two wrong
packages are tainting the whole staging area.
(This phenomenon has been already seen with libmudflap, libc, ... in
angstrom-stable [1])

But...why not fix these two immediately?

Andrea


[1]
ERROR: QA Issue: libmudflap.la failed sanity test (installed) in path
/OE/angstrom-tmp//staging/arm-angstrom-linux-gnueabi/lib
NOTE: a QA error occured but will not be logged because QA_LOG is not set
ERROR: QA Issue: libsupc++.la failed sanity test (installed) in path
/OE/angstrom-tmp//staging/arm-angstrom-linux-gnueabi/lib
NOTE: a QA error occured but will not be logged because QA_LOG is not set
ERROR: QA Issue: libmudflapth.la failed sanity test (installed) in path
/OE/angstrom-tmp//staging/arm-angstrom-linux-gnueabi/lib
NOTE: a QA error occured but will not be logged because QA_LOG is not set
ERROR: QA Issue: libstdc++.la failed sanity test (installed) in path
/OE/angstrom-tmp//staging/arm-angstrom-linux-gnueabi/lib
NOTE: a QA error occured but will not be logged because QA_LOG is not set

Re: QA Logs now on tinderbox

[Koen Kooi]

Andrea Adami wrote:
>> These two are the most common:
>
> Well, it is clear to me these are 'cruft' in staging. Two wrong
> packages are tainting the whole staging area.
> (This phenomenon has been already seen with libmudflap, libc, ... in
> angstrom-stable [1])
>
> But...why not fix these two immediately?

The .pc.in files need to get fixed, since fixing them when they are 
already in staging means that you are shipping from .pc files in -dev 
packages.

regards,

Koen



>
> Andrea
>
>
> [1]
> ERROR: QA Issue: libmudflap.la failed sanity test (installed) in path
> /OE/angstrom-tmp//staging/arm-angstrom-linux-gnueabi/lib
> NOTE: a QA error occured but will not be logged because QA_LOG is not set
> ERROR: QA Issue: libsupc++.la failed sanity test (installed) in path
> /OE/angstrom-tmp//staging/arm-angstrom-linux-gnueabi/lib
> NOTE: a QA error occured but will not be logged because QA_LOG is not set
> ERROR: QA Issue: libmudflapth.la failed sanity test (installed) in path
> /OE/angstrom-tmp//staging/arm-angstrom-linux-gnueabi/lib
> NOTE: a QA error occured but will not be logged because QA_LOG is not set
> ERROR: QA Issue: libstdc++.la failed sanity test (installed) in path
> /OE/angstrom-tmp//staging/arm-angstrom-linux-gnueabi/lib
> NOTE: a QA error occured but will not be logged because QA_LOG is not set

Re: QA Logs now on tinderbox

[Jeremy Lainé]

> But...why not fix these two immediately?

I have fixed python-pycairo, the problem here was that setup.py was
re-generating pycairo.pc every single time it was run, so patching the
file with sed did no good.

Instead we now generate pycairo.pc from pycairo.pc.in ourselves using sed.

Will look into Orbit-2.0.pc if I have a moment.

Cheers,
Jeremy