10399 2016-10-07 22:10:20 +0000 bitbake is unable to handle exceptions past the clean_environment() call 2017-12-06 17:11:08 +0000 1 1 7 Build System, Metadata & Runtime BitBake bitbake unspecified x86 Multiple RESOLVED FIXED https://bugzilla.yoctoproject.org/show_bug.cgi?id=10397 High critical 2.2 M4 1 benjamin.esquivel anibal.limon brian.avery poky.bs.watcher poky.watcher --- --- No (bug/feature does not impact docs) oldest_to_newest 67069 0 benjamin.esquivel 2016-10-07 22:10:20 +0000 When bitbake --server-only is called, any exception, handled or unhandled; that occurs after this line: cleanedvars = bb.utils.clean_environment() from bitbake/lib/bb/main.py, produces an infinite loop of cleanliness. An example of this is bug 10397. 67070 1 benjamin.esquivel 2016-10-07 22:18:59 +0000 An induced example of this bug can be found at the poky-contrib branch besquive/such-clean: http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=besquive/such-clean which places a handled exception right after the point where it will loop endlessly. it is worth noting that the exception could happen on further lines than this induced example, like with bug 10397. 67242 2 benjamin.esquivel 2016-10-13 21:11:41 +0000 Forgot to add the steps to reproduce: 1. clone the git repo 2. get the code from the besquive/such-clean branch (stimulates an exception) http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=besquive/such-clean 3. run the init build env script 4. start a bitbake server, i.e. $ bitbake --server-only -t xmlrpc -B localhost:1234 5. watch the fireworks 67243 3 anibal.limon 2016-10-13 21:34:04 +0000 The loop is on, File "/home/alimon/repos/pokyro/bitbake/lib/bb/event.py", line 158, in print_ui_queue Due of that function is called atexit, if you move the registry of bb.event.LogHandler after bb.utils.clean_environment() it will fix the problem because clean_environment() is calling logger.debug, more investigation is needed. diff --git a/bitbake/lib/bb/main.py b/bitbake/lib/bb/main.py index 19ee729..992e879 100755 --- a/bitbake/lib/bb/main.py +++ b/bitbake/lib/bb/main.py @@ -435,19 +435,15 @@ def bitbake_main(configParams, configuration): bb.msg.init_msgconfig(configParams.verbose, configuration.debug, configuration.debug_domains) + # Clear away any spurious environment variables while we stoke up the cooker + cleanedvars = bb.utils.clean_environment() + # Ensure logging messages get sent to the UI as events handler = bb.event.LogHandler() if not configParams.status_only: # In status only mode there are no logs and no UI logger.addHandler(handler) 67245 4 anibal.limon 2016-10-13 22:04:20 +0000 The bug is caused because bb.event.LogHandler adds events to ui_queue when is called causing an infinite loop when interate over ui_queue at print_ui_queue. 67246 5 anibal.limon 2016-10-13 22:05:04 +0000 Also happens in bitbake proceess not only server mode. 67249 6 anibal.limon 2016-10-13 23:12:07 +0000 Patch sent to, http://lists.openembedded.org/pipermail/bitbake-devel/2016-October/008153.html 67295 7 anibal.limon 2016-10-17 14:47:23 +0000 Fixed at, http://git.openembedded.org/bitbake/commit/?id=46fecca9d531a07788b5cac8b2dc6a8267d8b6d0