Bug 10890

Summary: Selftest OePkgdataUtilTests fails on poky-tiny distro
Product: [QA/Testing] Build Testing Reporter: Leonardo Sandoval Gonzalez <leonardo.sandoval.gonzalez>
Component: generalAssignee: Leonardo Sandoval Gonzalez <leonardo.sandoval.gonzalez>
Status: VERIFIED FIXED QA Contact: oscar lopez arandas <oscarx.lopez.arandas>
Severity: normal    
Priority: Medium+ CC: benjamin.esquivel, jose.perez.carranza, juan.m.cruz.alcaraz, ross.burton
Version: 2.3   
Target Milestone: 2.3 M4   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
oe-selftest none

Description Leonardo Sandoval Gonzalez 2017-01-06 22:31:20 UTC
If DISTRO is set to poky-tiny and oe-selftest --run-all is executed, the OePkgdataUtilTests test case fails because the distro uses musl instead of glibc target, the latter being used as a target in several places.

Some log obtained from local AB:

----snip----
======================================================================
ERROR [0.000s]: setUpClass (oeqa.selftest.pkgdata.OePkgdataUtilTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/ab/autobuilder/yocto-worker/nightly-oe-selftest-poky-tiny/build/meta/lib/oeqa/selftest/pkgdata.py", line 19, in setUpClass
    bitbake('glibc busybox zlib bash')
  File "/home/ab/autobuilder/yocto-worker/nightly-oe-selftest-poky-tiny/build/meta/lib/oeqa/utils/commands.py", line 143, in bitbake
    return runCmd(cmd, ignore_status, timeout, **options)
  File "/home/ab/autobuilder/yocto-worker/nightly-oe-selftest-poky-tiny/build/meta/lib/oeqa/utils/commands.py", line 121, in runCmd
    raise AssertionError("Command '%s' returned non-zero exit status %d:\n%s" % (command, result.status, result.output))
AssertionError: Command 'bitbake  glibc busybox zlib bash' returned non-zero exit status 1:
NOTE: Started PRServer with DBfile: /home/ab/autobuilder/yocto-worker/nightly-oe-selftest-poky-tiny/build/build/cache/prserv.sqlite3, IP: 127.0.0.1, PORT: 36969, PID: 32313
Loading cache...done.
ERROR: Nothing PROVIDES 'glibc'
ERROR: glibc was skipped: incompatible with host i586-poky-linux-musl (not in COMPATIBLE_HOST)
Loaded 1320 entries from dependency cache.

Summary: There was 1 ERROR message shown, returning a non-zero exit code.
----snip----
Comment 1 Leonardo Sandoval Gonzalez 2017-03-29 23:42:50 UTC
patch sent and tracked in  https://patchwork.openembedded.org/series/6064/
Comment 2 Leonardo Sandoval Gonzalez 2017-03-30 21:16:19 UTC
v1 was rejected due to proposed logic. instead a new series was sent, this time replacing glibc for zlib as suggested by rburton. patch sent and tracked at

https://patchwork.openembedded.org/series/6093/
Comment 3 Ross Burton 2017-04-03 13:34:19 UTC
Merged in OE-Core b77cf437e89a2ec21de6a69d5e34736925f1eeba.
Comment 4 oscar lopez arandas 2017-04-18 16:03:23 UTC
If DISTRO is set to poky-tiny and oe-selftest --run-all is executed, the OePkgdataUtilTests test case fails 

testimage: core-image-sato-core2-32.wic
 
Build Configuration:
BB_VERSION        = "1.33.3"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "universal"
TARGET_SYS        = "i686-poky-linux"
MACHINE           = "core2-32"
DISTRO            = "poky - tiny"
DISTRO_VERSION    = "2.2+snapshot-20170417"
TUNE_FEATURES     = "m32 core2"
COMMIT: eff56e4f0d59b1d965a68e4f009b7f07717b7edd

    STEPS:
git clone git://git.yoctoproject.org/poky"

b)In poky directory checkout on the desired commit:

$ git checkout <commit-id>

3. Source the environment, from poky directory

 $ cd ~/poky 

$ source oe-init-build-env

4. Edit local.conf. PATH
 5. In ~poky/build directory, in command line, type the following commands:

$ bitbake rpm psplash run-postinsts
$ bitbake package-index

NOTE: After finishing the tasks, copy the image manifest (core-image-sato-sdk-genericx86.manifest) and the testdata.json (core-image-sato-sdk-genericx86.testdata.json) from autobuilder at the following path: "~poky/build/tmp/deploy/images/genericx86/" ( if "/tmp/deploy/images/genericx86" does not exist create new directories with this path)

$ bitbake core-image-sato-sdk -c testimage

$ oe-selftest --run-all

EXPECTED OUTCOME:
the OePkgdataUtilTests test case fails 

ACTUAL OUTCOME:
the OePkgdataUtilTests test case successfully

RESULTS  IN  ATTACHMENT
Comment 5 oscar lopez arandas 2017-04-18 16:12:32 UTC
Created attachment 3733 [details]
oe-selftest
Comment 6 Leonardo Sandoval Gonzalez 2017-04-24 15:00:45 UTC
(In reply to comment #4)
> If DISTRO is set to poky-tiny and oe-selftest --run-all is executed, the
> OePkgdataUtilTests test case fails 
> 
> testimage: core-image-sato-core2-32.wic
>  
> Build Configuration:
> BB_VERSION        = "1.33.3"
> BUILD_SYS         = "x86_64-linux"
> NATIVELSBSTRING   = "universal"
> TARGET_SYS        = "i686-poky-linux"
> MACHINE           = "core2-32"
> DISTRO            = "poky - tiny"
> DISTRO_VERSION    = "2.2+snapshot-20170417"
> TUNE_FEATURES     = "m32 core2"
> COMMIT: eff56e4f0d59b1d965a68e4f009b7f07717b7edd
> 
>     STEPS:
> git clone git://git.yoctoproject.org/poky"
> 
> b)In poky directory checkout on the desired commit:
> 
> $ git checkout <commit-id>
> 
> 3. Source the environment, from poky directory
> 
>  $ cd ~/poky 
> 
> $ source oe-init-build-env
> 
> 4. Edit local.conf. PATH
>  5. In ~poky/build directory, in command line, type the following commands:
> 
> $ bitbake rpm psplash run-postinsts
> $ bitbake package-index
> 
> NOTE: After finishing the tasks, copy the image manifest
> (core-image-sato-sdk-genericx86.manifest) and the testdata.json
> (core-image-sato-sdk-genericx86.testdata.json) from autobuilder at the
> following path: "~poky/build/tmp/deploy/images/genericx86/" ( if
> "/tmp/deploy/images/genericx86" does not exist create new directories with
> this path)
> 
> $ bitbake core-image-sato-sdk -c testimage
> 
> $ oe-selftest --run-all
> 
> EXPECTED OUTCOME:
> the OePkgdataUtilTests test case fails 
> 
> ACTUAL OUTCOME:
> the OePkgdataUtilTests test case successfully
> 
> RESULTS  IN  ATTACHMENT


Oscar, so we should reopen this one, right?

Can you please attached the whole log? The current attach has just all test PASSED so it does not help much.