diff options
| author |   Richard Purdie <richard.purdie@linuxfoundation.org> | 2019-07-02 11:28:32 +0100 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2019-07-02 12:00:36 +0100 |
| commit | 4b9ab675cebb427ab8ad0c56c7b37eed50a2a39e (patch) | |
| tree | e231371234f6c6563cb6ab181f7e629dbe33f4c4 /lib/bb/main.py | |
| parent | 55631da1336589e583e8341a655179f7714ab3fe (diff) | |
| download | bitbake-4b9ab675cebb427ab8ad0c56c7b37eed50a2a39e.tar.gz | |
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.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'lib/bb/main.py')
| -rwxr-xr-x | lib/bb/main.py | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/lib/bb/main.py b/lib/bb/main.py index bd1161996..a1226886c 100755 --- a/lib/bb/main.py +++ b/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) |