openembedded-core.git/meta/classes/ptest.bbclass, branch fido

ptest: Work from PTEST_ENABLED, not DISTRO_FEATURES

2014-05-08T11:56:42+00:00

Some classes of recipe disable ptest even though its in DISTRO_FEATURES
(e.g. nativesdk). We shouldn't attempt to build ptest packages when
its disabled. This replaces some DISTRO_FEATURE checks with PTEST_ENABLED
checks instead.

Signed-off-by: Richard Purdie 
Signed-off-by: Saul Wold

Globally replace 'base_contains' calls with 'bb.utils.contains'

2014-04-25T16:10:58+00:00

The base_contains is kept as a compatibility method and we ought to
not use it in OE-Core so we can remove it from base metadata in
future.

Signed-off-by: Otavio Salvador 
Signed-off-by: Richard Purdie

ptest: Don't enable ptest for nativesdk and cross-canadian packages

2014-03-11T14:59:30+00:00

The ptest is useful in context of deployment to the target hence
we don't need ptest for nativesdk and cross-canadian packages

Signed-off-by: Tudor Florea 
Signed-off-by: Saul Wold 
Signed-off-by: Richard Purdie

meta/recipes: Remove virtclass references

2014-02-12T14:18:00+00:00

The virtclass overrides will go away at some point (apart from the multilib one).
Change them all to class-xxx instead since people enjoy copy and pasting them.

Signed-off-by: Richard Purdie

ptest: d.keys() is slow, use a list instead

2014-01-14T11:50:47+00:00

Unfortunately d.keys is extremely slow. Using a list in this case should be
fine since the addtask lines are immediately above the code and aren't
going to change often.

Signed-off-by: Richard Purdie

ptest.bblass: Fix package QA issues when disabled

2014-01-14T11:33:16+00:00

When the ptest distro feature is disabled, a ptest directory is still
created in the install phase, This directory is not cleaned up or
consumed by any package and will throw a QA error, e.g.

ERROR: QA Issue: glib-2.0: Files/directories were installed but not
shipped
  /usr/lib/glib-2.0/ptest
ERROR: QA run found fatal errors. Please consider fixing them.
ERROR: Function failed: do_package_qa

This is caused by the do_install_ptest_base[cleandirs] attribute which
is not setup to be conditional on ptest being enabled.

This patch refactors the use of PTEST_ENABLED in the *ptest_base tasks,
replacing the conditional execution with the removal of the tasks from
the build, this prevents any part (including cleandirs) of the ptest
tasks from executing when disabled.

Signed-off-by: Nathan Rossi 
Signed-off-by: Saul Wold

ptest: Disable for native recipes

2013-12-20T12:25:21+00:00

We don't use or otherwise care about ptest for native recipes. Its therefore
pointless to take the performance hit for them and we can disable them.

(From OE-Core rev: f3d35bb4719d0b8f8e6fc5976e9dbfc0e2019c2e)

Signed-off-by: Richard Purdie

ptest: Fix dependency/ordering issue

2013-12-20T12:25:21+00:00

We've seen occasional issues on the autobuilder where files appear during
do_populate_sysroot and this is due to the ptest installation happening
in parallel. This fixes the order to be deterministic.

(From OE-Core rev: 0ed1641d870f4bb5735aeeb7bd29cc196e61b7cc)

Signed-off-by: Richard Purdie

ptest: ensure do_install_ptest_base task runs in fakeroot context

2013-12-03T17:35:34+00:00

As this task is installing files into $D it needs to run inside pseudo so that
special permissions and owners are preserved.

Signed-off-by: Ross Burton 
Signed-off-by: Richard Purdie

classes/ptest: do not set EXCLUDE_FROM_WORLD

2013-10-30T17:27:15+00:00

Various normal recipes that we expect to build during a world build now
inherit this class; it cannot therefore set EXCLUDE_FROM_WORLD.

Signed-off-by: Paul Eggleton 
Signed-off-by: Richard Purdie