From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: ed.bartosh@linux.intel.com
Cc: "markus.Lehtonen" <markus.Lehtonen@intel.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 01/11] devtool: make 2 functions public
Date: Wed, 02 Sep 2015 16:22:09 +0100 [thread overview]
Message-ID: <1441207329.24871.70.camel@linuxfoundation.org> (raw)
In-Reply-To: <20150902135445.GA5916@linux.intel.com>
On Wed, 2015-09-02 at 16:54 +0300, Ed Bartosh wrote:
> On Wed, Sep 02, 2015 at 02:16:58PM +0300, Jussi Kukkonen wrote:
> > On 30 August 2015 at 19:08, Ed Bartosh <ed.bartosh@linux.intel.com> wrote:
> > >
> > > Moved standard.py:_parse_recipe -> __init__.py:parse_recipe and
> > > standard.py:_get_recipe_file -> __init__.py:get_recipe_file
> > > to be able to call them from other modules.
> >
> > Hi Ed,
> >
> > Can you take a look if the failures in
> > https://autobuilder.yoctoproject.org/main/builders/nightly-oe-selftest/builds/173/steps/Running%20oe-selftest/logs/stdio
> > are related to this patch (there's lots of "NameError: global name
> > '_parse_recipe' is not defined")
> >
>
> The autobuilder log looks very strange to me. I don't see any mentioning
> of _parse_recipe in standard.py on master. Moreover, there is no
> _prep_extract_operation function mentioned in traceback.
>
> I've just run failed test and it passed without any issues.
>
>
> It looks like autobuilder messed the code from some old branch and tests
> from master.
Its building master-next:
http://git.yoctoproject.org/cgit.cgi/poky/log/?h=master-next
and its therefore probably the devtool patches from Markus that are at
fault and need rebasing after your changes?
Cheers,
Richard
next prev parent reply other threads:[~2015-09-02 15:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-30 16:08 [PATCH 00/11] Improve build-image plugin Ed Bartosh
2015-08-30 16:08 ` [PATCH 01/11] devtool: make 2 functions public Ed Bartosh
2015-09-02 11:16 ` Jussi Kukkonen
2015-09-02 13:54 ` Ed Bartosh
2015-09-02 15:22 ` Richard Purdie [this message]
2015-08-30 16:08 ` [PATCH 02/11] devtool: build-image: stop using add_md5 Ed Bartosh
2015-08-30 16:08 ` [PATCH 03/11] Revert "devtool: make add_md5 a public API" Ed Bartosh
2015-08-30 16:08 ` [PATCH 04/11] devtool: build-image: rename LOG -> logger Ed Bartosh
2015-08-30 16:08 ` [PATCH 05/11] devtool: build-image: improve help and description Ed Bartosh
2015-08-30 16:08 ` [PATCH 06/11] devtool: build-image: filter out recipes Ed Bartosh
2015-08-30 16:08 ` [PATCH 07/11] devtool: build-image: generate notification callback Ed Bartosh
2015-08-30 16:08 ` [PATCH 08/11] devtool: build-image: add extra logging Ed Bartosh
2015-08-30 16:08 ` [PATCH 09/11] devtool: build-image: remove <image>.bbappend Ed Bartosh
2015-08-30 16:08 ` [PATCH 10/11] devtool: build-image: add comments Ed Bartosh
2015-08-30 16:08 ` [PATCH 11/11] oe-selftest: test devtool build-image plugin Ed Bartosh
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=1441207329.24871.70.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=ed.bartosh@linux.intel.com \
--cc=markus.Lehtonen@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