**** BEGIN LOGGING AT Wed Mar 23 02:59:57 2022
Mar 23 07:35:24 <mckoan> good morning
Mar 23 18:19:21 <cb5r> My dunfell build hangs after  a couple of minutes in compiling. debug doesnt show anything suspicious - its just that the progress stays the same forever and there is no CPU load. What can be the cause of such behavior?
Mar 23 18:37:44 <khem> some sort of deadlock perhaps
Mar 23 18:38:19 <khem> Check bitbake-cookerdaemon.log
Mar 23 18:38:31 <khem> and it might have some hints maybe
Mar 23 18:42:30 <cb5r> khem: Thanks for the tip - I'll check that!
Mar 23 19:36:48 <rburton> cb5r: pstree -p -l $(pgrep Cooker)
Mar 23 19:37:04 <rburton> that will give you a nice tree of the bitbake main process and all of the tasks it has spawned
Mar 23 19:37:27 <rburton> if there's no actual jobs below the workers, bitbake has hung. otherwise you'll hopefully see a process that has hung.
Mar 23 19:37:57 <rburton> cb5r: also is that reproducible with plain oe-core/poky or do you need vendor layers? same recipe that hangs every time?
Mar 23 19:38:19 <rburton> a relatively common thing is a build is sitting there waiting for interactive input and hasn't noticed that stdin is disconnected
Mar 23 21:51:25 <cb5r> <rburton> "cb5r: also is that reproducible..." <- I think it's related to the vendor layer. I had a successful poky-only build the other day which was similarly new. But I'll have to verify tomorrow...
Mar 23 21:53:46 <cb5r> There seems to always be qtbase-native involved @ do_compile...
Mar 23 22:33:28 <rburton> Good old ps can tell you if it’s got a stalled process in the build or if it’s bitvake itself that has hung
**** ENDING LOGGING AT Thu Mar 24 02:59:56 2022