public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-core@lists.openembedded.org,
	openembedded-devel@lists.openembedded.org
Subject: Re: State of bitbake world, Failed tasks 2014-04-28
Date: Tue, 29 Apr 2014 20:00:12 +0200	[thread overview]
Message-ID: <20140429180012.GK2486@jama> (raw)
In-Reply-To: <20140428025029.GG2486@jama>

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

On Mon, Apr 28, 2014 at 04:50:29AM +0200, Martin Jansa wrote:
> Be aware that qemux86-64 log is there, but it wasn't complete so it
> isn't included in this report.
> 
> It isn't complete, because with this number of failed recipes rm_work
> wasn't able to keep tmpdir small enough for my 55G tmpfs, biggest chunk
> was eaten by chromium and mongodb:
> 593M    tmp-eglibc/work/qemux86_64-oe-linux/linux-yocto-tiny-kexecboot
> 6.8G    tmp-eglibc/work/core2-64-oe-linux/mongodb
> 20G     tmp-eglibc/work/core2-64-oe-linux/chromium
> 
> Khem sent couple of patches for B!=S issues, bit thanks to him!
> 
> I have local patch to set B=S/autotools-brokensep for remaining failing
> recipes, but I'll wait a bit more for people to send fixes.

Be aware that failures in this report are just small part of whole B!=S
issues. After setting B=S in them more issues were found in recipes
which were "hidden" before because of failing dependency in first run.

Now I'm in 3rd round of adding B=S and with ~180 recipes having this it
still fails in couple newly revealed ones - I'll send the list when it's
complete (and list of failing recipes is the same as last report before
B!=S or better)

It sounds terrible, but changing the default to B!=S was good thing, we
can easily work-around it by B=S/autotools-brokensep and we'll get the
advantages of it at least in recipes which aren't broken.

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

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

      reply	other threads:[~2014-04-29 17:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-28  2:50 State of bitbake world, Failed tasks 2014-04-28 Martin Jansa
2014-04-29 18:00 ` 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=20140429180012.GK2486@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@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