From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH V3 2/4] selftest: imagefeatures: skip tests based on distro features and supported fstypes
Date: Wed, 11 Jan 2017 14:06:29 -0600 [thread overview]
Message-ID: <7761b4f4-aa4b-bf5b-646a-e5af208a8d7e@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LYDAbGZ4E_adYLFGCQ84Fq7Cfs6PJsBqJmapzkemTnAdw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2014 bytes --]
On 01/11/2017 11:27 AM, Burton, Ross wrote:
>
> On 9 January 2017 at 17:45,
> <leonardo.sandoval.gonzalez@linux.intel.com
> <mailto:leonardo.sandoval.gonzalez@linux.intel.com>> wrote:
>
> +++ b/meta/lib/oeqa/selftest/imagefeatures.py
> @@ -77,6 +77,9 @@ class ImageFeatures(oeSelfTest):
> AutomatedBy: Daniel Istrate
> <daniel.alexandrux.istrate@intel.com
> <mailto:daniel.alexandrux.istrate@intel.com>>
> """
>
> + if 'opengl' not in get_bb_var('DISTRO_FEATURES'):
> + self.skipTest('opengl not present on DISTRO_FEATURES
> so core-image-clutter cannot be built')
> +
> # Build a core-image-clutter
> bitbake('core-image-clutter')
>
>
> This test is pretty pointless, lets just delete it.
why is this pointless? if this is the case, we should then remove the
core-image-clutter.bb target.
> @@ -91,6 +94,10 @@ class ImageFeatures(oeSelfTest):
> AutomatedBy: Daniel Istrate
> <daniel.alexandrux.istrate@intel.com
> <mailto:daniel.alexandrux.istrate@intel.com>>
> """
>
> + distro_features = get_bb_var('DISTRO_FEATURES')
> + if not ('opengl' in distro_features and 'wayland' in
> distro_features):
> + self.skipTest('neither opengl nor wayland present on
> DISTRO_FEATURES so core-image-weston cannot be built')
> +
> features = 'DISTRO_FEATURES_append = " wayland"\n'
> features += 'CORE_IMAGE_EXTRA_INSTALL += "wayland weston"'
> self.write_config(features)
>
>
> This test is 90% nonsense, let's fix it whilst we're here. After
> checking that opengl and wayland are in DISTRO_FEATURES it can just
> build core-image-weston: DISTRO_FEATURES doesn't need appending as it
> already has wayland in, and CORE_IMAGE_EXTRA_INSTALL doesn't need
> extending as core-image-weston obviously already contains weston.
>
> Ross
[-- Attachment #2: Type: text/html, Size: 4356 bytes --]
next prev parent reply other threads:[~2017-01-11 19:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-09 17:44 [PATCH V3 0/4] Skip selftests depending on distro and its features leonardo.sandoval.gonzalez
2017-01-09 17:45 ` [PATCH V3 1/4] selftest: devtool: use distro agnostic recipes for devtool checks leonardo.sandoval.gonzalez
2017-01-09 17:45 ` [PATCH V3 2/4] selftest: imagefeatures: skip tests based on distro features and supported fstypes leonardo.sandoval.gonzalez
2017-01-11 17:27 ` Burton, Ross
2017-01-11 20:06 ` Leonardo Sandoval [this message]
2017-01-12 13:19 ` Burton, Ross
2017-01-09 17:45 ` [PATCH V3 3/4] selftest: runtime-test: skip image-install test for poky-tiny leonardo.sandoval.gonzalez
2017-01-09 17:45 ` [PATCH V3 4/4] selftest: sstatetests: skip glibc-initial tests and use a more generic image leonardo.sandoval.gonzalez
2017-01-11 17:29 ` Burton, Ross
2017-01-11 20:08 ` Leonardo Sandoval
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7761b4f4-aa4b-bf5b-646a-e5af208a8d7e@linux.intel.com \
--to=leonardo.sandoval.gonzalez@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox