From 53138165bc1098f2a80be19065dd6f5a30cb6431 Mon Sep 17 00:00:00 2001 From: Richard Purdie Date: Tue, 2 Jul 2019 11:28:32 +0100 Subject: 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 --- bitbake/lib/bb/main.py | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'bitbake/lib/bb/main.py') 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): else: logger.info("Retrying server connection (#%d)... (%s)" % (tryno, traceback.format_exc())) if not retries: - bb.fatal("Unable to connect to bitbake server, or start one") + bb.fatal("Unable to connect to bitbake server, or start one (server startup failures would be in bitbake-cookerdaemon.log).") + bb.event.print_ui_queue() if retries < 5: time.sleep(5) -- cgit v1.2.3-54-g00ecf