From: Jason Wessel <jason.wessel@windriver.com>
To: "Damian, Alexandru" <alexandru.damian@intel.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: about oe-init-build-env: Allow startup with and without memres
Date: Fri, 3 Jan 2014 08:19:37 -0600 [thread overview]
Message-ID: <52C6C6F9.70007@windriver.com> (raw)
In-Reply-To: <CAJ2CSBtesiTjc-0m6jSVwuTX0QZto=YgXNH0UzoZFc6qPK=M0g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]
On 01/03/2014 07:09 AM, Damian, Alexandru wrote:
> Hi Jason,
>
> I noticed that this patch *oe-init-build-env: Allow startup with and without memres* will kill any existing bitbake server when oe-init-build-env is started. I think this always happens since I see no way to source oe-init-build-env when BBSERVER is set.
>
> I'm trying to figure out a better solution, since simply stopping the server will leave toaster in an inconsistent state, if the server was started through toaster.
>
> Can you please tell me what behaviour are you trying to get out of the system ? Let's try to find something that will also work for Toaster.
It seems to me there must be a corner case, which should be easy enough to fix. If the BBSERVER is set, it should simply attach to the existing instance, assuming the instance is reachable. There is some code that was added to validate the bitbake server instance is healthy or it will get shutdown.
Do you have a step by step set of instructions to duplicate the behavior you are inquiring about or a bugzilla case I can take a peek at?
Thanks,
Jason.
[-- Attachment #2: Type: text/html, Size: 1904 bytes --]
next prev parent reply other threads:[~2014-01-03 14:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 13:09 about oe-init-build-env: Allow startup with and without memres Damian, Alexandru
2014-01-03 14:19 ` Jason Wessel [this message]
2014-01-03 14:42 ` Jason Wessel
2014-01-06 17:18 ` Damian, Alexandru
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=52C6C6F9.70007@windriver.com \
--to=jason.wessel@windriver.com \
--cc=alexandru.damian@intel.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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.