All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: bitbake-devel@lists.openembedded.org
Subject: Re: Couple of nasty bitbake issues
Date: Thu, 16 Jun 2011 16:35:04 -0700	[thread overview]
Message-ID: <4DFA9328.8040605@gmail.com> (raw)
In-Reply-To: <1308232450.15712.436.camel@rex>

On 06/16/2011 06:54 AM, Richard Purdie wrote:
> We have two nasty bitbake issues I've found:
>
> a) Our event handlers don't behave quite as you'd expect due to the use
> of global namespace.
>
> Basically, if you *ever* register an eventhandler, even in an optional
> class like native or nativesdk, your will always subsequently get called
> for any event.
>
> This means a handler in native.bbclass will see parsing events for a
> recipe which doesn't use it. The problem comes from ast.py:
>
>      all_handlers = {}
>      for var in bb.data.getVar('__BBHANDLERS', d) or []:
>          # try to add the handler
>          handler = bb.data.getVar(var, d)
>          bb.event.register(var, handler)
>
> Since we register the handlers but never un-register them or only call
> the ones which the current recipe uses.
>
> I can work around this for now but we really should fix this.
>
> b) The none server is totally broken for logging during parsing. Trying
> to cram two combine two pieces of code into one main loop turns out not
> to work so well.
>
> The first problem is that any events coming from the sub processes
> forked off during parallel parsing don't get sent to the server/UI. I
> know this has been commented on by various people, this is the root
> cause. I was able to fix that by borrowing queue code from the process
> server, so far so good.
>
> The problem then is the logger, since the logger in the UI uses the same
> namespace and setup as the one in the server. The one in the server is
> supposed to fire() events, the one in the UI is then meant to write them
> to the console. Trying to do both things in the same process goes
> horribly wrong. I have a hacky fix where each event is just seen twice
> but it doesn't look like an easy problem to solve. I'm unable to find an
> easy way to setup two loggers in parallel copying the config from one to
> the other which is ideally what is needed.

Does something like this can help
http://www.valuedlessons.com/2008/04/events-in-python.html

>
> I like the none server as its simple to debug. At present its looking
> like it might be too ugly to fix this though. My hacks are:
>
> http://git.yoctoproject.org/cgit.cgi/poky-contrib/commit/?h=rpurdie/ml&id=a3a130b3c6ca760066ca830eb46fa472ecb84c88
>
> Cheers,
>
> Richard
>
>
>
>
>
>
> _______________________________________________
> bitbake-devel mailing list
> bitbake-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel




  parent reply	other threads:[~2011-06-16 23:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-16 13:54 Couple of nasty bitbake issues Richard Purdie
2011-06-16 14:45 ` Jeremy Puhlman
2011-06-16 23:35 ` Khem Raj [this message]
2011-06-17  1:59 ` Khem Raj

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=4DFA9328.8040605@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=bitbake-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.