Openembedded Core Discussions
 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-06-02
Date: Tue, 10 Jun 2014 13:40:30 +0200	[thread overview]
Message-ID: <20140610114030.GG2433@jama> (raw)
In-Reply-To: <20140610100722.GC2433@jama>

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

On Tue, Jun 10, 2014 at 12:07:22PM +0200, Martin Jansa wrote:
> On Mon, Jun 02, 2014 at 10:49:50AM +0200, Martin Jansa wrote:
> > This build still contains huge patch setting B = S or inherit for
> > autotools-brokensep for all recipes which were failing in earlier
> > master builds.
> 
> http://www.openembedded.org/wiki/Bitbake_World_Status
> 
> == Failed tasks 2014-06-10 ==
> 
> === common (17) ===
>     * meta-openembedded/meta-efl/recipes-efl/efl/efl_1.10.0.bb, do_compile

I'll look into this one (as it's caused by my pending commit and doesn't fail on my local machine)

>     * meta-openembedded/meta-gnome/recipes-gnome/libgsf/libgsf_1.14.26.bb, do_compile
>     * meta-openembedded/meta-networking/recipes-support/curlpp/curlpp_0.7.3.bb, do_compile
>     * meta-openembedded/meta-networking/recipes-support/lksctp-tools/lksctp-tools_1.0.16.bb, do_compile
>     * meta-openembedded/meta-oe/recipes-connectivity/libnet/libnet_1.1.6.bb, do_configure
>     * meta-openembedded/meta-oe/recipes-devtools/python/python-cython_0.20.1.bb, do_package
>     * meta-openembedded/meta-oe/recipes-devtools/python/python-pyyaml_3.10.bb, do_compile
>     * meta-openembedded/meta-oe/recipes-multimedia/id3lib/id3lib_3.8.3.bb, do_configure
>     * meta-openembedded/meta-oe/recipes-navigation/omgps/omgps_svn.bb, do_compile
>     * meta-openembedded/meta-oe/recipes-support/daemonize/daemonize_git.bb, do_configure
>     * meta-openembedded/meta-oe/recipes-support/eject/eject_2.1.5.bb, do_compile
>     * meta-openembedded/meta-xfce/recipes-apps/xfce4-notifyd/xfce4-notifyd_0.2.2.bb, do_compile
>     * meta-openembedded/meta-xfce/recipes-apps/xfce4-screenshooter/xfce4-screenshooter_1.8.1.bb, do_compile
>     * meta-qt5/recipes-qt/maliit/maliit-framework-qt5_git.bb, do_compile

Fixed in master-next and jansa/master branches (I forgot to push it
before starting new build).

>     * meta-qt5/recipes-qt/qt5/qtwayland_git.bb, do_install

Fixed in master-next and jansa/master branches (I forgot to push it
before starting new build).

>     * meta-smartphone/meta-fso/recipes-freesmartphone/python/python-pyrtc_git.bb, do_compile
>     * meta-smartphone/meta-shr/recipes-shr/shr/python-phoneutils_git.bb, do_compile
> 
> === common-x86 (3) ===
>     * meta-browser/recipes-browser/chromium/chromium_35.0.1916.114.bb, do_compile
>     * meta-browser/recipes-mozilla/firefox/firefox_10.0.11esr.bb, do_compile
>     * openembedded-core/meta/recipes-bsp/grub/grub_2.00.bb, do_package

RP asked for more details about this one (and volunteered to look into
it - thanks!)

OE qemux86-64@ ~/oe/shr-core-branches/shr-core $ '/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/sysroots/x86_64-linux/usr/lib/rpm/bin/debugedit' -b '/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/core2-64-oe-linux' -d '/usr/src/debug' -i -l '/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/core2-64-oe-linux/grub/2.00-r1/debugsources.list' '/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/core2-64-oe-linux/grub/2.00-r1/package/usr/lib/grub/i386-pc/uhci.module'
/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/sysroots/x86_64-linux/usr/lib/rpm/bin/debugedit: elf_update: invalid section alignment

workdir, rpm-sstate and few more logs included in 58MB 
http://logs.nslu2-linux.org/buildlogs/oe/oe-shr-core-branches//log.world.20140610_021320.log/grub.tar.bz2

> === qemuarm (0) ===
> 
> === qemux86 (0) ===
> 
> === qemux86_64 (1) ===
>     * meta-openembedded/meta-oe/recipes-benchmark/libhugetlbfs/libhugetlbfs_git.bb, do_compile
> 
> === Number of failed tasks ===
> {| class=wikitable
> |-
> ||qemuarm       ||17    ||http://logs.nslu2-linux.org/buildlogs/oe/oe-shr-core-branches//log.world.20140606_153039.log/
> |-
> ||qemux86       ||20    ||http://logs.nslu2-linux.org/buildlogs/oe/oe-shr-core-branches//log.world.20140609_094000.log/
> |-
> ||qemux86_64    ||21    ||http://logs.nslu2-linux.org/buildlogs/oe/oe-shr-core-branches//log.world.20140610_021320.log/
> |}
> 



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

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

  reply	other threads:[~2014-06-10 11:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-10 10:07 State of bitbake world, Failed tasks 2014-06-02 Martin Jansa
2014-06-10 11:40 ` Martin Jansa [this message]
2014-06-12 11:06   ` Richard Purdie
2014-06-10 15:40 ` akuster@mvista
2014-06-20  9:57 ` [oe] " Richard Purdie
2014-06-20 10:24   ` Koen Kooi
2014-06-21  9:04     ` Paul Eggleton
2014-06-21  8:51   ` Martin Jansa
  -- strict thread matches above, loose matches on Subject: below --
2014-06-02  8:49 Martin Jansa

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=20140610114030.GG2433@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