10731 2016-11-27 20:41:22 +0000 bitbake --observe-only doesn't work with memres 2026-02-10 15:02:37 +0000 1 1 7 Build System, Metadata & Runtime BitBake bitbake 2.2 x86 Multiple NEW Medium+ normal 6.99 13023 1 bluelightning pavel liezhi.yang pavel poky.bs.watcher poky.watcher randy.macleod richard.purdie --- --- No (bug/feature does not impact docs) oldest_to_newest 68619 0 bluelightning 2016-11-27 20:41:22 +0000 bitbake --observe-only is supposed to capture and display events sent by the server, but it doesn't seem to be working. If I start it before running bitbake to build something, it exits when the build starts with the following error: ----------- snip ----------- $ BBSERVER=localhost:-1 bitbake --observe-only Traceback (most recent call last): File "/home/paul/poky/poky/bitbake/bin/bitbake", line 48, in <module> cookerdata.CookerConfiguration())) File "/home/paul/poky/poky/bitbake/lib/bb/main.py", line 511, in bitbake_main configParams) File "/home/paul/poky/poky/bitbake/lib/bb/ui/knotty.py", line 343, in main includelogs, loglines, consolelogfile = _log_settings_from_server(server) File "/home/paul/poky/poky/bitbake/lib/bb/ui/knotty.py", line 328, in _log_settings_from_server raise BaseException(error) BaseException: Not able to execute not readonly commands in readonly mode ----------- snip ----------- If I instead run it after I start the bitbake build, it times out: ----------- snip ----------- $ BBSERVER=localhost:-1 bitbake --observe-only Traceback (most recent call last): File "/home/paul/poky/poky/bitbake/bin/bitbake", line 48, in <module> cookerdata.CookerConfiguration())) File "/home/paul/poky/poky/bitbake/lib/bb/main.py", line 496, in bitbake_main server_connection.setupEventQueue() File "/home/paul/poky/poky/bitbake/lib/bb/server/xmlrpc.py", line 337, in setupEventQueue self.events = uievent.BBUIEventQueue(self.connection, self.clientinfo) File "/home/paul/poky/poky/bitbake/lib/bb/ui/uievent.py", line 72, in __init__ raise Exception(errmsg) Exception: Could not register UI event handler. Error: Cooker is busy: running, host 127.0.0.1, port 34833 WARNING: Could not register UI event handler. Error: Cooker is busy: running, host 127.0.0.1, port 34833, retry WARNING: Could not register UI event handler. Error: Cooker is busy: running, host 127.0.0.1, port 34833, retry WARNING: Could not register UI event handler. Error: Cooker is busy: running, host 127.0.0.1, port 34833, retry WARNING: Could not register UI event handler. Error: Cooker is busy: running, host 127.0.0.1, port 34833, retry WARNING: Could not register UI event handler. Error: Cooker is busy: running, host 127.0.0.1, port 34833, retry ----------- snip ----------- 73732 1 bluelightning 2017-06-06 11:09:08 +0000 We really need to add a test for --observe-only at the same time. 74191 2 bluelightning 2017-06-15 08:40:26 +0000 The first issue (starting the --observe-only instance first) appears to be solved in master at least, but the second is still present. It would be nice if there was a way to keep it alive so that you can continuously watch the server. 74912 3 liezhi.yang 2017-07-11 03:20:48 +0000 Hi Paul, I'd like to work on it if you are fine with that. 74915 4 bluelightning 2017-07-11 07:21:53 +0000 Certainly, thanks Robert! 76510 5 liezhi.yang 2017-09-05 01:12:59 +0000 The bitbake --observer doesn't work atm, we need go on working on it in 2.5 94326 6 randy.macleod 2022-11-01 19:53:08 +0000 Medium+ bugs should use an M* milestone so pick M2. 100096 7 randy.macleod 2024-10-31 15:09:25 +0000 Bulk move of 5.1 bugs to 5.2. -- YP bug review (Randy)