From: mariano.lopez@linux.intel.com
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 00/10] Allow to install packages in the DUT during runtime testing
Date: Tue, 24 May 2016 12:44:09 +0000 [thread overview]
Message-ID: <cover.1464092933.git.mariano.lopez@linux.intel.com> (raw)
From: Mariano Lopez <mariano.lopez@linux.intel.com>
This series enable the functionality to install packages in the DUT
during runtime testing. Such packages must had been build previously
by bitbake and the packages are specified using a JSON file. This
functionality works with testimage and with testexport.
A documentation draft has been submitted in bug 9672 to be added to
the Reference Manual.
This address several bugs:
- 7850 (not solved completely)
- 8478
- 8694
- 8536
The following changes since commit c7e614c438706fb3ed7520b4990ebb3973366942:
useradd: Fix infinite build loop (2016-05-23 10:33:45 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib mariano/bug7850v2
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=mariano/bug7850v2
Mariano Lopez (10):
testexport.bbclass: Stop exporting test context
oetest.py: Move getTests() outside loadTests() method
oeqa/utils/package_manager.py: Add get_package_manager()
oetest.py: Add json file support to specify packages needed in runtime
tests
oetest.py: Add extract_packages() to RuntimeTestContext class
oetest.py: Add support to copy unextracted packages for runtime
testing
lib/oe/package_manager.py: Add pkgpath to dict returned by
package_info
oetest.py: Add install/uninstall functionality for DUTs
cpio: Add native variant
testimage.bbclass: Make dependency of cpio when using RPMs
meta/classes/testexport.bbclass | 33 +++--
meta/classes/testimage.bbclass | 47 ++++++-
meta/lib/oe/package_manager.py | 41 +++---
meta/lib/oeqa/oetest.py | 239 ++++++++++++++++++++++++++++++---
meta/lib/oeqa/utils/package_manager.py | 29 ++++
meta/recipes-extended/cpio/cpio_v2.inc | 2 +
6 files changed, 347 insertions(+), 44 deletions(-)
create mode 100644 meta/lib/oeqa/utils/package_manager.py
--
2.6.6
next reply other threads:[~2016-05-24 20:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 12:44 mariano.lopez [this message]
2016-05-24 12:44 ` [PATCH 01/10] testexport.bbclass: Stop exporting test context mariano.lopez
2016-05-24 12:44 ` [PATCH 02/10] oetest.py: Move getTests() outside loadTests() method mariano.lopez
2016-05-24 12:44 ` [PATCH 03/10] oeqa/utils/package_manager.py: Add get_package_manager() mariano.lopez
2016-05-24 12:44 ` [PATCH 04/10] oetest.py: Add json file support to specify packages needed in runtime tests mariano.lopez
2016-05-24 12:44 ` [PATCH 05/10] oetest.py: Add extract_packages() to RuntimeTestContext class mariano.lopez
2016-05-24 12:44 ` [PATCH 06/10] oetest.py: Add support to copy unextracted packages for runtime testing mariano.lopez
2016-05-24 12:44 ` [PATCH 07/10] lib/oe/package_manager.py: Add pkgpath to dict returned by package_info mariano.lopez
2016-05-24 12:44 ` [PATCH 08/10] oetest.py: Add install/uninstall functionality for DUTs mariano.lopez
2016-05-24 12:44 ` [PATCH 09/10] cpio: Add native variant mariano.lopez
2016-05-24 12:44 ` [PATCH 10/10] testimage.bbclass: Make dependency of cpio when using RPMs mariano.lopez
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.1464092933.git.mariano.lopez@linux.intel.com \
--to=mariano.lopez@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.