From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Voicu, Cristiana" <cristiana.voicu@intel.com>
Cc: bitbake-devel <bitbake-devel@lists.openembedded.org>
Subject: Re: [RFC PATCH] Split runqueue to use bitbake-worker
Date: Thu, 06 Jun 2013 09:16:38 +0100 [thread overview]
Message-ID: <1370506598.1640.74.camel@ted> (raw)
In-Reply-To: <BE68E9C8E0850C43B0F0B0B7D57FA5AE2E7D6013@IRSMSX105.ger.corp.intel.com>
On Thu, 2013-06-06 at 08:00 +0000, Voicu, Cristiana wrote:
> I have tested your patches with Hob, but I can't see the issue for it.
> In Hob you can change the configuration at the begging (before
> starting the build task), so when the bitbake-worker will start will
> take the changed configuration. I have tested it changing the
> sstate-cache dir, and everything worked ok (it created a new dir for
> sstate-cache). Also, in Hob I can see the warnings you placed to see
> if the worker is working properly.
>
> Is there something I'm missing?
When I start hob I see a number of "setVariable" commands running. These
get set in the core configuration but they do not get set on the
bitbake-worker side.
I don't know which variables get set this way but they won't have any
effect after this patch.
Which variables get set this way? (Easiest way to find out would be to
add print statements to the code I guess).
We may need to change those writes to become actual editing of
local.conf to set values for example.
Cheers,
Richard
prev parent reply other threads:[~2013-06-06 8:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 13:59 [RFC PATCH] Split runqueue to use bitbake-worker Richard Purdie
2013-06-06 8:00 ` Voicu, Cristiana
2013-06-06 8:16 ` Richard Purdie [this message]
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=1370506598.1640.74.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=cristiana.voicu@intel.com \
/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.