From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH v2 0/1] oe-selftest: devtool: fix test for changes in lzo recipe
Date: Thu, 7 Dec 2017 23:03:39 +1300 [thread overview]
Message-ID: <cover.1512640717.git.paul.eggleton@linux.intel.com> (raw)
A fix for one of the devtool oe-selftest tests to handle Ross's lzo
acinclude.m4 fix.
Changes since v1:
* Some uncommitted changes to the test recipe got wiped out by the bit at
the end of the test that resets the test changes, hence the checksums
were missing from the recipe - add the missing stuff back n.
* Add a check to ensure there's no uncommitted changes before proceeding
with the test (as per other tests that have this resetting)
The following changes since commit a7cd9d1183be603777fc9c8c448281fe01224f7b:
lib/oe/utils: remove param_bool() (2017-12-02 11:24:38 +0000)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/devtool-selftest-fix
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=paule/devtool-selftest-fix
Paul Eggleton (1):
oe-selftest: devtool: fix test for changes in lzo recipe
.../recipes-test/devtool/devtool-test-local/file1 | 1 +
.../recipes-test/devtool/devtool-test-local/file2 | 1 +
.../recipes-test/devtool/devtool-test-local_6.03.bb | 15 +++++++++++++++
meta/lib/oeqa/selftest/cases/devtool.py | 16 ++++++++++------
4 files changed, 27 insertions(+), 6 deletions(-)
create mode 100644 meta-selftest/recipes-test/devtool/devtool-test-local/file1
create mode 100644 meta-selftest/recipes-test/devtool/devtool-test-local/file2
create mode 100644 meta-selftest/recipes-test/devtool/devtool-test-local_6.03.bb
--
2.9.5
next reply other threads:[~2017-12-07 10:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 10:03 Paul Eggleton [this message]
2017-12-07 10:03 ` [PATCH v2 1/1] oe-selftest: devtool: fix test for changes in lzo recipe Paul Eggleton
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=cover.1512640717.git.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
/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