Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Christopher Larson <kergoth@gmail.com>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
	Christopher Larson <chris_larson@mentor.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCHv3 0/6] recipetool/devtool/oe-selftest: pull from BBPATH
Date: Sat, 25 Jul 2015 17:09:09 +0100	[thread overview]
Message-ID: <1437840549.821.171.camel@linuxfoundation.org> (raw)
In-Reply-To: <cover.1437663603.git.chris_larson@mentor.com>

On Thu, 2015-07-23 at 12:57 -0700, Christopher Larson wrote:
> From: Christopher Larson <chris_larson@mentor.com>
> 
> Ensures that recipetool and devtool pull plugins from layers, and
> oe-selftest will pull tests from layers.
> 
> Unrelated to that, also prevents a traceback on parsing failure, and adds
> a tiny feature to appendsrc to facilitate reuse by other sub-commands.
> 
> [v3 Update] Fixed the commit message for `devtool: also load plugins from
> BBPATH` to match the implementation. Split up `recipetool: also load plugins
> from BBPATH` into two commits with clear commit messages.
> 
> [v2 Update] `devtool: also load plugins from BBPATH` was fixed, so it no longer
> breaks the devtool selftests.

I know there are some issues with oe-selftest on the autobuilder at the
moment, specifically master results in things like:

https://autobuilder.yoctoproject.org/main/builders/nightly-oe-selftest/builds/93

however when I apply this and your other series, the autobuilder
oe-selftest does this:

https://autobuilder.yoctoproject.org/main/builders/nightly-oe-selftest/builds/92/steps/Running%20oe-selftest/logs/stdio

which is substantially worse. I can't immediately see what the issue is
but the two runs above pretty much bisect this down to the patch series.
I'm therefore reluctant to merge these until we can figure out what is
going on...

Cheers,

Richard



  parent reply	other threads:[~2015-07-25 16:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-23 19:57 [PATCHv3 0/6] recipetool/devtool/oe-selftest: pull from BBPATH Christopher Larson
2015-07-23 19:58 ` [PATCHv3 1/7] recipetool: catch BBHandledException from parsing Christopher Larson
2015-07-23 19:58 ` [PATCHv3 2/7] recipetool.append: add extralines arg to appendsrc Christopher Larson
2015-07-23 19:58 ` [PATCHv3 3/7] recipetool: also load plugins from BBPATH Christopher Larson
2015-07-23 19:58 ` [PATCHv3 4/7] recipetool: parse global args early Christopher Larson
2015-07-23 19:58 ` [PATCHv3 5/7] devtool: also load plugins from BBPATH Christopher Larson
2015-07-23 19:58 ` [PATCHv3 6/7] oe-selftest: obey oeqa.selftest.__path__ Christopher Larson
2015-07-23 19:58 ` [PATCHv3 7/7] oe-selftest: add libdirs from BBPATH to sys.path Christopher Larson
2015-07-24 15:51 ` [PATCHv3 0/6] recipetool/devtool/oe-selftest: pull from BBPATH Paul Eggleton
2015-07-25 16:09 ` Richard Purdie [this message]
2015-07-25 19:18   ` Christopher Larson
2015-07-27 12:16     ` Richard Purdie
2015-07-27 17:59       ` Christopher Larson

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=1437840549.821.171.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=chris_larson@mentor.com \
    --cc=kergoth@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.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