summaryrefslogtreecommitdiffstats
path: root/bitbake/lib/bb/main.py
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2019-07-02 11:28:32 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2019-07-03 17:00:57 +0100
commit53138165bc1098f2a80be19065dd6f5a30cb6431 (patch)
tree393b82c6926ca68af1b5e2bbcd22d9e84b316c7a /bitbake/lib/bb/main.py
parent0a0cc5ff2ee02d50b18a67f329a4e46b3e9d5a00 (diff)
downloadpoky-53138165bc1098f2a80be19065dd6f5a30cb6431.tar.gz
bitbake: main: Ensure log messages are printed when no UI starts
If the UI hasn't started, no messages are printed to the console until the server starts. This is confusing, particularly if the server never starts. Flush the UI queue through the simply handler upon connection retry so the user sees the messages they're supposed to be seeing. Also point the user at the logfile for hints about why this may be. (Bitbake rev: 4b9ab675cebb427ab8ad0c56c7b37eed50a2a39e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/lib/bb/main.py')
-rwxr-xr-xbitbake/lib/bb/main.py3
1 files changed, 2 insertions, 1 deletions
diff --git a/bitbake/lib/bb/main.py b/bitbake/lib/bb/main.py
index bd11619966..a1226886c0 100755
--- a/bitbake/lib/bb/main.py
+++ b/bitbake/lib/bb/main.py
@@ -468,7 +468,8 @@ def setup_bitbake(configParams, configuration, extrafeatures=None):
468 else: 468 else:
469 logger.info("Retrying server connection (#%d)... (%s)" % (tryno, traceback.format_exc())) 469 logger.info("Retrying server connection (#%d)... (%s)" % (tryno, traceback.format_exc()))
470 if not retries: 470 if not retries:
471 bb.fatal("Unable to connect to bitbake server, or start one") 471 bb.fatal("Unable to connect to bitbake server, or start one (server startup failures would be in bitbake-cookerdaemon.log).")
472 bb.event.print_ui_queue()
472 if retries < 5: 473 if retries < 5:
473 time.sleep(5) 474 time.sleep(5)
474 475