Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Status Update
Date: Tue, 18 Mar 2014 13:09:35 +0000	[thread overview]
Message-ID: <1395148175.3808.83.camel@ted> (raw)

I was travelling in the last week which limited the time I could spend
on various issues.

The week has mostly been seeing patches being tested on the autobuilder
in MUT/master-next with a view to ironing out bugs before code merges.

Pending Patches
===============

I did manage to flush some queued patches into the various repositories
after testing on the autobuilder. The current pending list is now:

* archiver rework patches (not had a chance to review yet)
* 3.14 kernel (not released yet, we have patches being tested, ongoing 
  perf issues but close to resolution with any luck)
* updated meta-yocto-bsp bsps for BBB and edge router
* Enabling B != S - Can't decide whether to push this or not. Have got 
  several known issues fixed up in layers (thanks Otavio). Martin, any 
  thoughts on this?
* pusleaudio 5.0?
* systemd 112?
* bitbake fetcher extension code for automated "upgrade" detection

We have had a number of these through testing cycles on the autobuilder,
systemd in particular should be ready to go in and I'll probably merge
that.

I'm not happy about the changes coming in as late as they are, equally,
I think the changes are work getting in. It will be ready when it is
ready...

Bitbake Changes
===============

The sigchld handler is continue to cause issues. Some are fixed but we
were seeing locked up processes on the autobuilder which appeared to be
trapped in waitpid. I've pushed some further patches to stop the code
doing bad things, I'm not 100% sure why it was breaking but the latest
builds seem to be behaving.

I'd advice people to keep up to date with master and report any issues
they find. Bonus marks for good reproducers, it makes things much faster
to fix!

I do want to get -S fixed for the release so some changes are pending
for that.

1.4.3
=====

There were sstate issues on the autobuilder, Paul backported the patch
which was confirmed as fixing the issue. We tried for another build, I
messed up the branches though (sorry Paul/Saul/Beth). We'll spin another
build when the autobuilder is free.


Cheers,

Richard




             reply	other threads:[~2014-03-18 13:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-18 13:09 Richard Purdie [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-10-03 12:01 Status Update Richard Purdie
2014-04-29  8:49 Richard Purdie
2014-04-29 11:29 ` Richard Purdie
2014-04-29 17:31   ` Otavio Salvador
2014-04-15 18:45 Richard Purdie
2014-04-08 12:25 Richard Purdie
2014-04-01 13:51 Richard Purdie
2014-03-24 11:53 Richard Purdie
2014-03-10  2:20 Richard Purdie
2014-03-10  2:43 ` Robert Yang
2013-07-01  7:01 Richard Purdie
2013-05-28 17:35 Richard Purdie
2013-05-28 19:34 ` Jack Mitchell
2013-05-07 12:45 Richard Purdie
2013-04-29 20:57 Richard Purdie
2013-03-20 23:45 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=1395148175.3808.83.camel@ted \
    --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