From: Joshua Lock <joshua.g.lock@linux.intel.com>
To: Patrick Ohly <patrick.ohly@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/4] meta-selftest: add selftest-ed recipes
Date: Fri, 10 Mar 2017 13:27:00 +0000 [thread overview]
Message-ID: <1489152420.3099.7.camel@linux.intel.com> (raw)
In-Reply-To: <1489089950.7785.374.camel@intel.com>
On Thu, 2017-03-09 at 21:05 +0100, Patrick Ohly wrote:
> On Wed, 2017-03-08 at 17:24 +0000, Joshua Lock wrote:
> > The oe-selftest oescripts.TestScripts.test_cleanup_workdir was
> > using
> > gzip and the GPLv2 variant to test cleanup of the workdir. This
> > broke
> > with the removal of GPLv2 recipes from OE-Core.
> >
> > Instead of relying on recipes in OE-Core remaining static we should
> > ensure that meta-selftest provides recipes required for the tests
> > to pass.
> > To that end we take a copy of the current GPLv2 and GPLv3 variants
> > of ed
> > and include them in meta-selftest as new recipes.
> > We chose ed over gzip as gzip has dependencies which would require
> > additional GPLv2 recipes to be included in meta-selftest.
>
> Wouldn't the test become faster when using artificial recipes, i.e.
> something which doesn't really need sources? Such an artificial
> recipe
> can use a local file as its "source", for example.
Indeed, that would make the test faster. I took a shorter route for
this series in an attempt to unblock M3, however I realise that the
bitbake targets used in oe-selftest could do with a consistent review.
I've filed an enhancement request to that effect:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=11142
> Or did I misunderstand something and the selftest doesn't really
> build
> ed?
It does build ed, which is an improvement over building gzip but not as
fast as something artificial.
Thanks for the feedback,
Joshua
next prev parent reply other threads:[~2017-03-10 13:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 17:24 [PATCH 1/4] chkconfig-alternatives-native: fix obey_variables Joshua Lock
2017-03-08 17:24 ` [PATCH 2/4] meta-selftest: add selftest-ed recipes Joshua Lock
2017-03-09 20:05 ` Patrick Ohly
2017-03-10 13:27 ` Joshua Lock [this message]
2017-03-10 13:38 ` Patrick Ohly
2017-03-08 17:24 ` [PATCH 3/4] lib/oeqa/selftest/oescripts: make test_cleanup_workdir use selftest-ed Joshua Lock
2017-03-08 17:24 ` [PATCH 4/4] lib/oeqa/selftest/bbtests: update test_non_gplv3 to " Joshua Lock
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=1489152420.3099.7.camel@linux.intel.com \
--to=joshua.g.lock@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=patrick.ohly@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