Bug 10956 - selftest: sstatetessts should use world instead of image targets, making it distro agnostic
Summary: selftest: sstatetessts should use world instead of image targets, making it d...
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 2.3
Hardware: x86 Multiple
: Medium enhancement
Target Milestone: 2.5 M2
Assignee: Leonardo Sandoval Gonzalez
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-01-23 18:38 UTC by Leonardo Sandoval Gonzalez
Modified: 2017-10-31 15:28 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Leonardo Sandoval Gonzalez 2017-01-23 18:38:25 UTC
There is already some partial work on this area [1], using a minimal instead of a sato image but at the end, the best is to use world, making the test case completely distro agnostic.

[1] http://lists.openembedded.org/pipermail/openembedded-core/2017-January/130897.html
Comment 1 Leonardo Sandoval Gonzalez 2017-08-29 14:04:27 UTC
The following commit created by RP solves partially this bug

commit 90c1bb7569e3c38cf406d726edb8cc719e4df3fc
Author: Richard Purdie <richard.purdie@linuxfoundation.org>
Date:   Fri Apr 7 15:26:30 2017 +0100

    selftest/sstatetests: Replace glibc-initial with linux-libc-headers
    
    The intent in these tests was to find something early in the bootstrap
    process to run tests against which didn't require long build times.
    This breaks with the removal of the glibc-initial do_build target.
    Replacing it with linux-libc-headers seems like a good choice
    and simplifies the conditionals too.
    
    (From OE-Core rev: c37d610272f9d0a506334ff9f724c025acace137)

but there are still some image targets that need to be replaced by world if possible.
Comment 2 Leonardo Sandoval Gonzalez 2017-08-31 15:51:48 UTC
This is an enhancement and medium, so changing proper settings.
Comment 3 Leonardo Sandoval Gonzalez 2017-09-26 16:26:40 UTC
Too late for M4. This is definitely not a priority (not breaking anything at current testing) so moving to 2.5M2.
Comment 4 Leonardo Sandoval Gonzalez 2017-10-31 15:28:37 UTC
comment 1 resolves this problem. There is no need to change the target to 'world', because all supported oe-core distros can construct current targets (defined on the test cases)