Bug 12239 - enable automated testing of non core layers with common usage
Summary: enable automated testing of non core layers with common usage
Status: RESOLVED FIXED
Alias: None
Product: Build Testing
Classification: QA/Testing
Component: general (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 4.99
Assignee: Unassigned
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-10-18 17:42 UTC by brian avery
Modified: 2022-06-02 16:34 UTC (History)
6 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Yes (doc changes required)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description brian avery 2017-10-18 17:42:06 UTC 
Some layers (meta-games, for instance) are not layers that are commonly built upon by a large number of developers (i realize this is opinion!).

Some layers are very commonly used as a basis for additional work. Examples that fall into this category (a VERY non complete list) are layers like 
meta-python
meta-perl
meta-networking
meta-filesystem
meta-virtualization
meta-<diverse, but finite others>

It would be very beneficial to the YP to be able to test (both build and runtime)the layer that are often the basis for other work, yet are not maintained in oe-core.
Comment 1 Richard Purdie 2020-05-21 08:30:51 UTC 
We now have meta-oe on the autobuilder and the TSC defined a policy for extending test coverage. Progress has therefore been made.
Comment 2 Randy MacLeod 2022-06-02 15:30:35 UTC 
We now have limited testing of meta-oe on the YP AB.
Comment 3 Richard Purdie 2022-06-02 16:34:09 UTC 
as well as meta-virtualization, meta-intel, meta-arm, meta-aws, meta-agl-core and a policy where we could add others.