Re: [OE-core] bitbake-server does not exit after build ends

["Böszörményi Zoltán" <zboszor@gmail.com>]

2023. 11. 28. 15:50 keltezéssel, Alexander Kanavin írta:
> On Tue, 28 Nov 2023 at 11:31, Zoltan Boszormenyi <zboszor@gmail.com> wrote:
>> The warning only occurs if os.fork() is called when
>> there are already Python threads.
>>
>> I guess the general performance uplift in Python 3.12
>> can trigger a pre-existing issue in bitbake more easily.
>>
>> It is entirely possible that the threads bitbake creates do not
>> exist yet with Python 3.11 and earlier at the time of executing
>> os.fork(). ¯\_(ツ)_/¯
> I think you might be too quick to jump to conclusions here.

Indeed.
I should have added "assuming Python is not the buggy party here".
Sorry.

>   I've fixed
> the async issue I've been observing (backporting
> https://github.com/python/cpython/commit/2e5d4e24ebcd671915427b6fd35a5b0eea412c4a
> ), and when running bitbake with 3.12 from buildtools-tarball,
> everything works fine, and I'm not seeing any leftover processes. Poky
> revision is current master:
> https://git.yoctoproject.org/poky/commit/?h=master&id=3e50e45917831d9da2d86e69fb908a1a78483b62

This means that 3.12.1 should fix this problem, and that release
is supposedly "imminent": 3.12.0 was released on 2023-10-02 and
subsequent bugfix releases are scheduled every two months.