All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] oe-selftest improvements
Date: Fri,  6 Nov 2015 13:16:57 +0000	[thread overview]
Message-ID: <cover.1446815768.git.paul.eggleton@linux.intel.com> (raw)

A fix for two tests plus an additional test for the bitbake-layers
show-recipes command.


The following changes since commit e44ed8c18e395b9c055aefee113b90708e8a8a2f:

  build-appliance-image: Update to jethro head revision (2015-11-03 14:02:57 +0000)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib paule/oe-selftest-1
  http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/oe-selftest-1

Paul Eggleton (3):
  oeqa/selftest/devtool: fix test if build directory is not inside
    COREBASE
  oeqa/selftest/layerappend: fix test if build directory is not inside
    COREBASE
  oe-selftest: add test for bitbake-layers show-recipes

 meta/lib/oeqa/selftest/bblayers.py    | 25 +++++++++++++++++++++++++
 meta/lib/oeqa/selftest/devtool.py     |  2 +-
 meta/lib/oeqa/selftest/layerappend.py |  9 ++++++---
 3 files changed, 32 insertions(+), 4 deletions(-)

-- 
2.1.0



             reply	other threads:[~2015-11-06 13:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-06 13:16 Paul Eggleton [this message]
2015-11-06 13:16 ` [PATCH 1/3] oeqa/selftest/devtool: fix test if build directory is not inside COREBASE Paul Eggleton
2015-11-06 13:16 ` [PATCH 2/3] oeqa/selftest/layerappend: " Paul Eggleton
2015-11-06 13:17 ` [PATCH 3/3] oe-selftest: add test for bitbake-layers show-recipes Paul Eggleton
  -- strict thread matches above, loose matches on Subject: below --
2020-06-03 20:07 [PATCH 0/3] oe-selftest improvements Paul Barker

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.1446815768.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 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.