12898 2018-08-23 21:25:17 +0000 Bitbake does not print server errors when there is no TTY 2018-11-15 08:34:51 +0000 1 1 7 Build System, Metadata & Runtime BitBake bitbake 5.99 x86 Multiple RESOLVED FIXED Medium+ normal 2.7 M1 1 bluelightning liezhi.yang poky.bs.watcher poky.watcher randy.e.witt randy.macleod --- --- No (bug/feature does not impact docs) oldest_to_newest 81425 0 bluelightning 2018-08-23 21:25:17 +0000 If the bitbake server fails to start (e.g. because of a sanity test failure when processing the configuration) and there is no TTY (e.g. when running inside Docker without -t) then the last 10 lines of bitbake-cookerdaemon.log will not be printed. This appears to be because the start marker that we need to figure out where the last server's messages start in the logfile does not get written to the file when there is no TTY. Log when there is no TTY: https://travis-ci.org/crops/poky-container/jobs/419770906 Log when there is a TTY: https://travis-ci.org/rewitt1/poky-container/jobs/419847827 (FYI the reason there is no TTY set normally for this container is because if there is one then you get progress/timer cruft in the output). 81455 1 richard.purdie 2018-08-30 14:38:28 +0000 We've seen this on jenkins and on buildbot on our autobuilder too. Its confusing as the error doesn't show in the logs and the user gets confused. 82183 2 liezhi.yang 2018-11-13 03:03:36 +0000 I tried: $ echo 'HOSTTOOLS += \"hello\"' >> conf/local.conf $ nohup bitbake -p It works as expected, there is a bitbake-cookerdaemon.log, and the last 10 logs printed. I also tried docke run <image> without -t, it also worked as expected. I suspect there is no bitbake-cookerdaemon.log when the error happened. I need more info to go on this work: * Do you still get the errors recently ? * Would you please provide detailed steps on how to reproduce it? I think that what can I do now is print an info when there is no bitbake-cookerdaemon.log 82204 3 randy.e.witt 2018-11-13 18:11:59 +0000 I just did a bisect and it looks like this issue was fixed with 74feaddda3b7cd5b3ab18d2f25bf5ef9581c9c47. 82235 4 liezhi.yang 2018-11-15 08:34:51 +0000 (In reply to comment #3) > I just did a bisect and it looks like this issue was fixed with > 74feaddda3b7cd5b3ab18d2f25bf5ef9581c9c47. Great, thanks. Fixed: 74feaddda3b7cd5b3ab18d2f25bf5ef9581c9c47