From: Martin Jansa <martin.jansa@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: Merging problems
Date: Mon, 22 Dec 2014 17:50:54 +0100 [thread overview]
Message-ID: <20141222165054.GE2465@jama> (raw)
In-Reply-To: <1419074109.13316.31.camel@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 1882 bytes --]
On Sat, Dec 20, 2014 at 11:15:09AM +0000, Richard Purdie wrote:
> So where are we at?
>
> Thanks to some great help from Ross, we have a number of patches merged
> and many of the issues in my last email have been addressed. I'm
> continuing to struggle with the kernel series. The last build on the
> autobuilder highlighted that:
>
> * there are problems in boot-directdisk.bbclass (have a fix)
> * there is a do_rootfs/do_package_qa race (have a fix)
> * the report-error.bbclass tasks could crash (have a fix)
> * the kernelmodule sanity tests were failing (have a fix)
> * qemumips gdb is failing to compile, probably due to new kernel
> headers (no fix as yet)
> * systemd sanity QA tests continue to fail on xorg and systemd-login
> (no fix as yet)
> * there are continuing problems with linux-imx from meta-fsl-arm, I
> thought these were addressed but clearly not :(
>
> Ideally I'd like to take some time off over the holidays but I can't see
> that happening until the patch queues are under some kind of control :(.
One of kernel patches merged last weekend seems to be causing all /usr/src/kernel
files to be installed in sysroot without sstate knowledge (and possibly
missing when kernel is reused from sstate)
sstate-find-cruft.sh from last world build now reports:
ERROR: 52961 issues were found.
ERROR: Following files are installed in sysroot, but not tracked by
sstate:
qemuarm/usr/src/kernel/.git
qemuarm/usr/src/kernel/.git/HEAD
...
qemuarm/usr/src/kernel/.meta
qemuarm/usr/src/kernel/.meta/cfg
qemuarm/usr/src/kernel/.meta/cfg/kernel-cache
qemuarm/usr/src/kernel/.meta/cfg/kernel-cache/00-README\
...
qemuarm/usr/src/kernel/.scmversion
qemuarm/usr/src/kernel/COPYING
qemuarm/usr/src/kernel/CREDITS
qemuarm/usr/src/kernel/Documentation
...
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2014-12-22 16:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 10:28 Merging problems Richard Purdie
2014-12-19 12:41 ` Richard Purdie
2014-12-19 13:07 ` Bruce Ashfield
2014-12-19 13:14 ` Bruce Ashfield
2014-12-19 13:15 ` Richard Purdie
2014-12-19 13:58 ` Bruce Ashfield
2014-12-20 11:15 ` Richard Purdie
2014-12-20 15:13 ` Bruce Ashfield
2014-12-20 22:17 ` Richard Purdie
2014-12-20 22:40 ` Richard Purdie
2014-12-21 2:04 ` Bruce Ashfield
2014-12-21 11:27 ` Richard Purdie
2014-12-21 12:35 ` Richard Purdie
2014-12-21 13:56 ` Richard Purdie
2014-12-22 3:40 ` Bruce Ashfield
2014-12-22 3:38 ` Bruce Ashfield
2014-12-20 19:19 ` Otavio Salvador
2014-12-20 22:14 ` Richard Purdie
2014-12-22 16:50 ` Martin Jansa [this message]
2014-12-22 17:00 ` Richard Purdie
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=20141222165054.GE2465@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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