The buildnot UI reports the build timed out with no output but the build looks like it completed. Worker: fedora35-ty-2 genericx86-alt target https://autobuilder.yoctoproject.org/typhoon/#/builders/103/builds/3818 We can see the step timing information here: https://autobuilder.yoctoproject.org/typhoon/api/v2/builders/103/builds/3818/steps/11 Translating those epoch values gives: 22 March 2022 17:21:42 22 March 2022 23:01:16 Logs saved here: https://autobuilder.yocto.io/pub/failed-builds-data/fedora35-genericx86-alt-20220322/ With the endtime on https://autobuilder.yocto.io/pub/failed-builds-data/fedora35-genericx86-alt-20220322/bitbake-cookerdaemon.log showing a time about 10 mins after the start and a clear server exit. This suggests the server really did complete and the UI hung at exit for some reason. Why? Don't know :(
I am suspicious of 1785558 14:31:16.523180 More than one thread left?: [<_MainThread(MainThread, started 139817764251456)>, <Thread(asyncio_0, started 139817658435136)>]
https://git.yoctoproject.org/poky/commit/?id=88fcf8422dd04372d73aacfef0ee50de09ef41bd and https://git.yoctoproject.org/poky/commit/?id=cff6c1a18d56e20d99d2331704dd490940c386e3 should handle the asyncio thread issue which is python 3.10 specific. Not sure if this will help the hang.
Possibly fixed by https://git.yoctoproject.org/poky/commit/bitbake?id=5940020cfb721d79111072b3cd5d581fff59561b (there was a similar bug I can't find right now)