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>

diff --git a/bitbake/lib/bb/main.py b/bitbake/lib/bb/main.py
index bd116199660a7f76399fb1fc27af07f0eeb91a71..a1226886c0d2872428e7f658337c88aff72e1fe0 100755 (executable)
--- 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)