From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Christopher Larson <kergoth@gmail.com>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCHv3 0/6] recipetool/devtool/oe-selftest: pull from BBPATH
Date: Mon, 27 Jul 2015 13:16:46 +0100 [thread overview]
Message-ID: <1437999406.821.240.camel@linuxfoundation.org> (raw)
In-Reply-To: <CABcZANnnqTczLS4B=663mrPOG7i3WoKXdkPONu0wScxgHdSMGw@mail.gmail.com>
On Sat, 2015-07-25 at 12:18 -0700, Christopher Larson wrote:
>
> On Sat, Jul 25, 2015 at 9:09 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> 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...
>
> Given that both failures have nothing to do with devtool, recipetool,
> or oe-selftest and are simply bitbake build failures as called by
> tests, I don’t really see how these could have anything to do with
> that, but understood.
FWIW, the issue is that you use the "xxx:do_unpack" syntax in one of the
tests. This breaks toaster.bbclass and once its broken, it stays broken
as its doing a split(":") on data in a file it never cleans up if the
function fails.
I've taken a fix which should avoid these issues. Will rerun a build
with that applied (and various other fixes) and hopefully we can then
get things merged.
Cheers,
Richard
next prev parent reply other threads:[~2015-07-27 12:17 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
2015-07-25 19:18 ` Christopher Larson
2015-07-27 12:16 ` Richard Purdie [this message]
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=1437999406.821.240.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--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