Openembedded Core Discussions
 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 fixes for devtool
Date: Thu,  7 May 2015 14:52:22 +0100	[thread overview]
Message-ID: <cover.1431006684.git.paul.eggleton@linux.intel.com> (raw)

Fix a couple of regressions in the oe-selftest tests for devtool (one 
caused by me, the other caused by the recent PN change in gcc-source),
plus one more improvement to how we deal with tap devices in the test
for "devtool deploy-target".


The following changes since commit 52d5ab7fcea7028ff1d10b3e2416c0179128ba71:

  bluez: update to 5.30 (2015-05-07 13:14:39 +0100)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib paule/devtool-selftests
  http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/devtool-selftests

Paul Eggleton (3):
  oe-selftest: devtool: fix broken URL in test_devtool_add_fetch
  devtool: fix for rename of gcc-source
  oe-selftest: devtool: add a proper test to see if tap devices exist

 meta/lib/oeqa/selftest/devtool.py | 22 ++++++++++++++++++++--
 scripts/lib/devtool/standard.py   |  2 +-
 2 files changed, 21 insertions(+), 3 deletions(-)

-- 
2.1.0



             reply	other threads:[~2015-05-07 13:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-07 13:52 Paul Eggleton [this message]
2015-05-07 13:52 ` [PATCH 1/3] oe-selftest: devtool: fix broken URL in test_devtool_add_fetch Paul Eggleton
2015-05-07 13:52 ` [PATCH 2/3] devtool: fix for rename of gcc-source Paul Eggleton
2015-05-07 13:52 ` [PATCH 3/3] oe-selftest: devtool: add a proper test to see if tap devices exist 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.1431006684.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