Bug 12239

Summary:	enable automated testing of non core layers with common usage
Product:	[QA/Testing] Build Testing	Reporter:	brian avery <brian.avery>
Component:	general	Assignee:	Unassigned <unassigned>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Medium+	CC:	akuster, bluelightning, joshuagloe, randy.macleod, richard.purdie, stephano
Version:	unspecified
Target Milestone:	4.99
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	Yes (doc changes required)

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.