All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH v2 0/2] improved killing bitbake server
Date: Tue,  5 Jan 2016 15:45:36 +0200	[thread overview]
Message-ID: <1452001538-25251-1-git-send-email-ed.bartosh@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LaxgVGcwkTL-3mzHeCtU+s42oMVwtm7Sbcb1YqErx2p=w@mail.gmail.com>

Hi,

Setup of event queue includes registering of UI handler.
This operation can fail when cooker is busy. However, there is
no need in registering UI handler for terminating the server.

This patchset makes server terminating to work without setting up
the event queue and registering UI handler. This should make
terminating server to work more reliably.

This should also help Toaster backend to restart bitbake server
and observer without getting "Could not register UI event handler"
errors.

Changes in v2: Fixed AttributeError: BitBakeProcessServerConnection instance has no attribute 'setupEventQueue'

Ed Bartosh (2):
  bitbake: xmplrpc: split connect method
  bitbake: main: kill server without queue setup

 bitbake/lib/bb/main.py            | 12 +++++++-----
 bitbake/lib/bb/server/__init__.py |  3 +++
 bitbake/lib/bb/server/xmlrpc.py   |  4 ++--
 3 files changed, 12 insertions(+), 7 deletions(-)

--
Regards,
Ed



  reply	other threads:[~2016-01-05 15:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-05  8:48 [PATCH 0/2] improved killing bitbake server Ed Bartosh
2016-01-05  8:48 ` [PATCH 1/2] bitbake: xmplrpc: split connect method Ed Bartosh
2016-01-05 15:21   ` Burton, Ross
2016-01-05 13:45     ` Ed Bartosh [this message]
2016-01-05 13:45       ` [PATCH v2 " Ed Bartosh
2016-01-05 13:45       ` [PATCH v2 2/2] bitbake: main: kill server without queue setup Ed Bartosh
2016-01-05  8:48 ` [PATCH " Ed Bartosh

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=1452001538-25251-1-git-send-email-ed.bartosh@linux.intel.com \
    --to=ed.bartosh@linux.intel.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.