On 2023-12-21 1:56 p.m., Martin Jansa wrote:
On Thu, Dec 21, 2023 at 7:47 PM Randy MacLeod <[email protected]> wrote:On 2023-11-28 4:26 a.m., Zoltan Boszormenyi via lists.openembedded.org <https://urldefense.com/v3/__http://lists.openembedded.org__;!!AjveYdw8EvQ!dmJtTKioa9DzcUCj9Bnd0SAhV_iwzhIPFdUGgYGvfCcHJTBSqwE1j07pX4x-RmoIfylxSh1gB9shlAshIeRlbYI0P5Q$> wrote:So it's not just Fedora, but Python 3.12 in general. Googling for problem with threads + fork reveals that it is indeed an issue even in C / POSIX: only the thread executing fork() will become part of the new process, but not the main process starting the thread or any other threads from the original process. The warning is justified, and apparently the issue not occurring in bitbake with previous Python versions is pure luck.FYI: Fixed in Fedora 39 if you update to get python-3.12.1-1 or later. But this fixes it only for bitbake master, right?
Even master might still have some problems. I can do a simple build of a package but in doing: $ bitbake -k world I see: NOTE: No reply from server in 30s (for command ping at 17:50:35.510798) After some time. I'm not going to try to debug it at this point in the day/year!
With bitbake 2.0 used in kirkstone I still see bitbake processes still running after the build is finished.
I didn't try kirkstone. Maybe Steve has that on his list of things to do in his spare time! ;-)
../Randy -- # Randy MacLeod # Wind River Linux
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#192854): https://lists.openembedded.org/g/openembedded-core/message/192854 Mute This Topic: https://lists.openembedded.org/mt/102826186/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
