Richard Purdie b2c39835bb bitbake: process/cooker: Allow UI process to know if the cooker was started successfully ...

Currently if the server fails to start, the user sees no error message and
the server will be repeatedly attempted to be started until some longer
timeouts expire. There are error messages in the cookerdeamon log but
nobody thinks to look there.

Add in a pipe which can be used to tell the starting process whether the cooker
did actually start or not. If it fails to start, no further attempts can be
made and if present, the log file can be shown to the user.

[YOCTO #11834]

(Bitbake rev: 57000d44beb1aeba37dfc70782b0d6418943acc5)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

2017-07-30 08:43:36 +01:00

..

bb

bitbake: process/cooker: Allow UI process to know if the cooker was started successfully

2017-07-30 08:43:36 +01:00

bblayers

bitbake: bitbake-layers: check layer dependencies before adding

2017-06-06 19:52:51 +01:00

bs4

bitbake: lib/bs4: Fix imports from html5lib >= 0.9999999/1.0b8

2016-12-07 10:43:20 +00:00

ply

bitbake: bitbake: Convert to python 3

2016-06-02 08:24:02 +01:00

progressbar

bitbake: lib: implement basic task progress support

2016-07-08 09:57:26 +01:00

prserv

bitbake: prserv/serv: Improve process exit handling

2017-07-24 16:57:14 +01:00

simplediff

bitbake: lib/bb/siggen: show word-diff for single-line values containing spaces

2017-04-10 23:00:32 +01:00

toaster

bitbake: toaster: trim build target input

2017-07-21 09:26:18 +01:00

codegen.py

bitbake: bitbake: Convert to python 3

2016-06-02 08:24:02 +01:00

pyinotify.py

bitbake: bitbake/pyinotify.py: Upgrade to py3 version

2016-06-02 08:24:02 +01:00