15641 2024-11-05 15:34:38 +0000 BB_CONSOLELOG is overwritten on 2nd+ runs when using memory resident BitBake 2026-06-17 15:24:35 +0000 1 1 7 Build System, Metadata & Runtime BitBake bitbake unspecified x86 Multiple RESOLVED FIXED Medium normal 6.1 M4 1 yoann.congal antonin.godard poky.bs.watcher poky.watcher randy.macleod yoann.congal --- --- Yes (doc changes required) oldest_to_newest 100112 0 yoann.congal 2024-11-05 15:34:38 +0000 When using "memory resident BitBake", the BB_CONSOLELOG is read from config when the server starts but, on the runs after that, any BB_CONSOLELOG config will be overwritten by the value read at the server start. How to reproduce: In local.conf BB_SERVER_TIMEOUT = "-1" BB_CONSOLELOG = "${LOG_DIR}/XXX.log" Ensure there is no resident bitbake server: bitbake --kill-server Read BB_CONSOLELOG: bitbake-getvar BB_CONSOLELOG => XXX.log Change BB_CONSOLELOG: BB_CONSOLELOG = "${LOG_DIR}/YYY.log" Re-read BB_CONSOLELOG: bitbake-getvar BB_CONSOLELOG => XXX.log # Here I was expecting YYY.log Restart bitbake to "fix" this: bitbake --kill-server bitbake-getvar BB_CONSOLELOG => YYY.log Note: this may be by design, the code is in https://git.openembedded.org/bitbake/tree/lib/bb/cooker.py#n290: if consolelog: self.data.setVar("BB_CONSOLELOG", consolelog) In any case, this behavior should be documented 100123 1 randy.macleod 2024-11-07 15:37:32 +0000 This is by design so that failures, when disconnected, go somewhere. 102199 2 antonin.godard 2025-06-06 07:45:01 +0000 Bulk move of bugs I am assigned to from Milestone 5.2 to 5.3M1. 105777 3 antonin.godard 2026-06-09 09:06:55 +0000 Yoann, I was reading this and was wondering how you actually start a "memory resident BitBake". I tried starting bitbake with --server-only but it eventually dies. Is there a way to have the bitbake server run permanently? 105785 4 yoann.congal 2026-06-09 12:18:14 +0000 (In reply to Antonin Godard from comment #3) > Yoann, I was reading this and was wondering how you actually start a "memory > resident BitBake". I tried starting bitbake with --server-only but it > eventually dies. Is there a way to have the bitbake server run permanently? I don't play with "--server-only". For me "memory resident BitBake" is a normal bitbake run with BB_SERVER_TIMEOUT != 0 Use "-1" for infinite timeout but I usually set it to 60 to save on parsing time in bitbake call sequence but not leave idle bb processes too long. See: https://docs.yoctoproject.org/ref-manual/variables.html#term-BB_SERVER_TIMEOUT 105796 5 antonin.godard 2026-06-10 08:30:08 +0000 Hi Yoann, I see thanks, I was able to reproduce the issue. There's also the -T parameter for controlling the timeout FWIW. I just sent a patch to document this behavior :) https://lore.kernel.org/r/20260610-bb-console-log-persistent-v1-1-5430d24061c3@bootlin.com 105908 6 antonin.godard 2026-06-17 15:24:35 +0000 Patch merged: https://git.openembedded.org/bitbake/commit/?id=b8bb48ed585d40ffa456744d74290d10fe186b85