Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: "Andreas Müller" <schnitzeltony@googlemail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>,
	openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [oe] State of bitbake world, Failed tasks 2017-08-09
Date: Fri, 11 Aug 2017 20:16:08 +0200	[thread overview]
Message-ID: <20170811181608.GA11833@jama> (raw)
In-Reply-To: <CALbNGRRdCu1oYc=SOf0LrENZ+tJhJMSTu20OvzBWo8BwMbQMUQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2607 bytes --]

On Fri, Aug 11, 2017 at 07:58:36PM +0200, Andreas Müller wrote:
> On Fri, Aug 11, 2017 at 6:45 PM, Martin Jansa <martin.jansa@gmail.com> wrote:
> >
> > firefox and mariadb fail like this only since conf/distro/include/security_flags.inc was included
> >
> > qtbase fails because of ptest addition as reported on ML
> >
> >> Kodi patch to use std::string was sent. mongodb needs something similar.
> >
> > The kodi patch from Andreas was already included in this build. Yours
> > kodi patch looks similar, but not backported from upstream.
> >
> > see:
> >> > 3a03560 kodi: fix build with latest gcc
> I checked the log and don't understand what happened: kodi on qemux86
> failed exactly with the error message I saw before fixing. Since the
> other qemus did not fail: are you sure my patch did not come in while
> build was already running?

Yes, that's possible (like for squid, maybe qtbase as well).

The problem is that qemux86 and qemux86-64 run on one builder, qemuarm
on another. Each build takes around 25-26 hours (depending on kind of
changes which were introduced since last time, almost any oe-core
upgrade means build from scratch, if I update just pending patches in
meta-oe/master-next, then it's 2-5 hours).

And this report is generated based on the state of qemuarm build.

So quite often I start all 3 at the same time, then some interesting
changes came in later, so qemux86-64 build picks them and because I know
it will take quite long time I re-trigger the qemuarm build to finish in
parallel (so qemux86 usually ends being the "oldest"). But to provide at
least some feedback I don't re-trigger another qemux86 build, because
that would add another day till the report is complete.

No of course another round is already running, hopefully I'll ignore the
temptation to add more changes to it while it's running and do something
better with my life - more consitent report should be available
tomorrow.

Regards,

> >
> >
> >> imagemagick issue is also taken care of
> >
> > is it? where? Notice that this includes also the 2nd imagemagick upgrade
> > which also already disappeared from the site.
> Randy suggested to skip imagemagick update until upstream stabilizes.
> >
> >> I have sent a patch for squid issue
> >
> > You mean this one?
> >> > e435561 squid: Add missing dependencies on openssl expat and libxml2
> >
> > it's already included (might be missing in qemux86 build which was
> > started first).
> >
> -> kodi?
> 
> Regards
> 
> Andreas

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]

      reply	other threads:[~2017-08-11 18:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-11  8:03 State of bitbake world, Failed tasks 2017-08-09 Martin Jansa
2017-08-11 15:59 ` [oe] " Khem Raj
2017-08-11 16:45   ` Martin Jansa
2017-08-11 17:58     ` Andreas Müller
2017-08-11 18:16       ` Martin Jansa [this message]

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=20170811181608.GA11833@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=schnitzeltony@googlemail.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