From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/6] wic: fix for #11017
Date: Wed, 22 Feb 2017 22:53:35 +0200 [thread overview]
Message-ID: <20170222205335.GA13229@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LZT_D4gXYRY__zWuDCY9zOKaHL1tmgqppP5=8qJzijn+Q@mail.gmail.com>
On Wed, Feb 22, 2017 at 04:38:55PM +0000, Burton, Ross wrote:
> Hi Ed,
>
> Something in your latest patchset is breaking selftest:
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-wic/builds/626/steps/CreateWicImages/logs/stdio
>
> The broken commit is somewhere in ross/mut-wic. Can you verify that I
> didn't leave something out, or otherwise chase this?
>
I couldn't reproduce this so far. Will investigate further.
Can you merge this patchset please?
http://lists.openembedded.org/pipermail/openembedded-core/2017-February/132854.html
The failure is most probably caused by patchset from this thread.
Regards,
Ed
> On 21 February 2017 at 15:23, Ed Bartosh <ed.bartosh@linux.intel.com> wrote:
>
> > Hi,
> >
> > This patchset improves handling of wic native tool dependencies and
> > fixes minor bugs in the wic code.
> >
> > The following changes since commit 9a0ddad5e178d16f302af2d05c3236
> > 8572849fd3:
> >
> > wic: pluginbase: use global dictionary (2017-02-20 11:58:28 +0200)
> >
> > are available in the git repository at:
> >
> > git://git.yoctoproject.org/poky-contrib ed/wic/wip
> > http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=ed/wic/wip
> >
> > Ed Bartosh (6):
> > wic: use 2 sysroots to find native executable
> > wic: use image recipe sysroot as default
> > wic: exec_native_cmd: improve debug message
> > wic: exec_native_cmd: fix undefined variable error
> > wic: add WKS_FILE_DEPENDS variable
> > wic: raise WicError instead of calling logger.error
> >
> > meta-selftest/recipes-test/images/wic-image-minimal.bb | 2 +-
> > meta/classes/image_types_wic.bbclass | 2 ++
> > scripts/lib/wic/plugins/source/bootimg-pcbios.py | 4 ++--
> > scripts/lib/wic/utils/misc.py | 13 +++++++++----
> > scripts/wic | 2 +-
> > 5 files changed, 15 insertions(+), 8 deletions(-)
> >
> > --
> > Regards,
> > Ed
> >
> > --
> > _______________________________________________
> > Openembedded-core mailing list
> > Openembedded-core@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-core
> >
--
--
Regards,
Ed
next prev parent reply other threads:[~2017-02-22 20:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 15:23 [PATCH 0/6] wic: fix for #11017 Ed Bartosh
2017-02-21 15:23 ` [PATCH 1/6] wic: use 2 sysroots to find native executable Ed Bartosh
2017-02-21 15:23 ` [PATCH 2/6] wic: use image recipe sysroot as default Ed Bartosh
2017-02-21 15:23 ` [PATCH 3/6] wic: exec_native_cmd: improve debug message Ed Bartosh
2017-02-21 15:23 ` [PATCH 4/6] wic: exec_native_cmd: fix undefined variable error Ed Bartosh
2017-02-21 15:23 ` [PATCH 5/6] wic: add WKS_FILE_DEPENDS variable Ed Bartosh
2017-02-21 15:23 ` [PATCH 6/6] wic: raise WicError instead of calling logger.error Ed Bartosh
2017-02-22 16:38 ` [PATCH 0/6] wic: fix for #11017 Burton, Ross
2017-02-22 20:53 ` Ed Bartosh [this message]
2017-02-23 10:18 ` Ed Bartosh
2017-02-23 10:39 ` Ed Bartosh
2017-02-23 14:08 ` Patrick Ohly
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=20170222205335.GA13229@linux.intel.com \
--to=ed.bartosh@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@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