From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Merging problems
Date: Fri, 19 Dec 2014 10:28:34 +0000 [thread overview]
Message-ID: <1418984914.13316.6.camel@linuxfoundation.org> (raw)
I want to give people a headsup that we're having problems merging
changes at the moment. We've been doing our best but the number of
things building up which are causing issues is overwheling our ability
to fix and stablise the build. It wasn't helped that I took a long
weekend's vacation last weekend. There are changes being made or tested
to the autobuilder which also isn't helping.
The kernel series has several issues:
* a random failure in do_kernel_configme [i]
* bzImage not being built for some machines [ii]
* non linux-yocto kernel failures [iii]
* the headers upgrade breaks socat (fix pending, thanks Bruce)
There was a change merged to bitbake which broken cups on lsb and
powertop due to unset variable problems. I have two pending fixes for
those.
For the last test build, we have 195 failures to dig through:
http://errors.yoctoproject.org/Errors/Search/Args/?items=150&page=1&query=99e7d5b9c736eb08a3853818a73c51676e7aa7ac
and we've not managed to dive into many of them. I don't have fixes for
the three kernel issues above.
So I'd ask that people be patient and if you have some time to help with
any of these problems, I'd welcome it. Most people are off on vacation
now which is going to leave me with a challenge.
Cheers,
Richard
[i] https://autobuilder.yoctoproject.org/main/builders/nightly-ppc-lsb/builds/129/steps/BuildImages/logs/stdio
[ii] https://autobuilder.yoctoproject.org/main/builders/minnow/builds/129/steps/BuildImages/logs/stdio
[iii] https://autobuilder.yoctoproject.org/main/builders/nightly-fsl-arm/builds/128/steps/BuildImages/logs/stdio
(5 unknown build failures in this one!)
https://autobuilder.yoctoproject.org/main/builders/nightly-fsl-ppc/builds/129/steps/BuildImages/logs/stdio
(only 3 here)
next reply other threads:[~2014-12-19 10:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 10:28 Richard Purdie [this message]
2014-12-19 12:41 ` Merging problems 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
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=1418984914.13316.6.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@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