[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openembedded-core
Subject:    Re: [OE-core] bitbake-server does not exit after build ends
From:       "Alexander Kanavin" <alex.kanavin () gmail ! com>
Date:       2023-12-31 10:03:03
Message-ID: CANNYZj_L=rEwhgdWLchdzHYgdWMrkZ4rizCKvmF8hXotBcKgnw () mail ! gmail ! com
[Download RAW message or body]

For what it's worth, I am not seeing any of these issues (hanging
processes after bitbake exit, timeouts on world builds with all
meta-oe-layers) with python 3.12 provided by buildtools-tarball. The
issues are probably real, but it's also possible python 3.12 per se is
not to blame.

It would probably help if you check if what you're seeing occurs with
python 3.12 from the tarball, which you can build from this branch:
https://git.yoctoproject.org/poky-contrib/log/?h=akanavin/py3.12
(the log in the web ui isn't updated yet, I just pushed)

Alex

On Fri, 22 Dec 2023 at 00:06, Randy MacLeod via lists.openembedded.org
<randy.macleod=windriver.com@lists.openembedded.org> wrote:
> 
> On 2023-12-21 1:56 p.m., Martin Jansa wrote:
> 
> On Thu, Dec 21, 2023 at 7:47 PM Randy MacLeod <randy.macleod@windriver.com> \
> wrote:
> > 
> > On 2023-11-28 4:26 a.m., Zoltan Boszormenyi via lists.openembedded.org 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 (#193086): https://lists.openembedded.org/g/openembedded-core/message/193086
Mute This Topic: https://lists.openembedded.org/mt/102826186/4454766
Group Owner: openembedded-core+owner@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [openembedded-core@marc.info]
-=-=-=-=-=-=-=-=-=-=-=-



[prev in list] [next in list] [prev in thread] [next in thread]