From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: Merging problems
Date: Sat, 20 Dec 2014 22:40:11 +0000 [thread overview]
Message-ID: <1419115211.13316.47.camel@linuxfoundation.org> (raw)
In-Reply-To: <54959211.9020504@windriver.com>
On Sat, 2014-12-20 at 10:13 -0500, Bruce Ashfield wrote:
> On 2014-12-20 6:15 AM, 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 :(.
>
> Let me know if there are one of these that you want me to take. I'm all
> for pitching in and getting everyone some down time.
Looks like I spoke too soon:
https://autobuilder.yoctoproject.org/main/builders/nightly-x86/builds/132/steps/BuildImages_1/logs/stdio
which seems to be a race over the kernel source directory. I'm guessing
the file in question is a temporary build artefact of lttng-modules
which was running at the same time? Any way we can avoid temp files in
the kernel source dir?
Cheers,
Richard
next prev parent reply other threads:[~2014-12-20 22:40 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 [this message]
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=1419115211.13316.47.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bruce.ashfield@windriver.com \
--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