16187 2026-03-03 08:58:08 +0000 AB-INT: bitbake: ForkingPickler: SemLock shared between fork and spawn context 2026-03-05 15:42:28 +0000 1 1 7 Build System, Metadata & Runtime BitBake bitbake unspecified x86 Multiple RESOLVED DUPLICATE 16184 AB-INT Medium normal 6.0 1 mathieu.dubois-briand tgamblin poky.bs.watcher poky.watcher randy.macleod --- --- No (bug/feature does not impact docs) oldest_to_newest 104469 0 mathieu.dubois-briand 2026-03-03 08:58:08 +0000 Another new AB-INT. This is probably related to #16184. I logged some errors in there, but the error is different enough so I create a separate entry. ERROR: An uncaught exception occurred in runqueue Traceback (most recent call last): File "/srv/pokybuild/yocto-worker/a-full/build/layers/bitbake/lib/bb/runqueue.py", line 1663, in execute_runqueue return self._execute_runqueue() ~~~~~~~~~~~~~~~~~~~~~~^^ File "/srv/pokybuild/yocto-worker/a-full/build/layers/bitbake/lib/bb/runqueue.py", line 1607, in _execute_runqueue retval = self.dump_signatures(dumpsigs) File "/srv/pokybuild/yocto-worker/a-full/build/layers/bitbake/lib/bb/runqueue.py", line 1718, in dump_signatures p.start() ~~~~~~~^^ File "/usr/lib64/python3.14/multiprocessing/process.py", line 121, in start self._popen = self._Popen(self) ~~~~~~~~~~~^^^^^^ File "/usr/lib64/python3.14/multiprocessing/context.py", line 224, in _Popen return _default_context.get_context().Process._Popen(process_obj) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^ File "/usr/lib64/python3.14/multiprocessing/context.py", line 300, in _Popen return Popen(process_obj) File "/usr/lib64/python3.14/multiprocessing/popen_forkserver.py", line 35, in __init__ super().__init__(process_obj) ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^ File "/usr/lib64/python3.14/multiprocessing/popen_fork.py", line 20, in __init__ self._launch(process_obj) ~~~~~~~~~~~~^^^^^^^^^^^^^ File "/usr/lib64/python3.14/multiprocessing/popen_forkserver.py", line 47, in _launch reduction.dump(process_obj, buf) ~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^ File "/usr/lib64/python3.14/multiprocessing/reduction.py", line 60, in dump ForkingPickler(file, protocol).dump(obj) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^ File "/usr/lib64/python3.14/multiprocessing/synchronize.py", line 109, in __getstate__ raise RuntimeError('A SemLock created in a fork context is being ' ...<2 lines>... 'multiprocessing objects and Process.') RuntimeError: A SemLock created in a fork context is being shared with a process in a spawn context. This is not supported. Please use the same context to create multiprocessing objects and Process. when serializing dict item 'rlock' when serializing bb.server.process.ConnectionReader state when serializing bb.server.process.ConnectionReader object when serializing dict item 'command_channel' when serializing bb.server.process.ProcessServer state when serializing bb.server.process.ProcessServer object when serializing dict item 'process_server' when serializing bb.cooker.BBCooker state when serializing bb.cooker.BBCooker object when serializing dict item 'cooker' when serializing bb.runqueue.RunQueue state when serializing bb.runqueue.RunQueue object when serializing tuple item 0 when serializing method reconstructor arguments when serializing method object when serializing dict item '_target' when serializing multiprocessing.context.Process state when serializing multiprocessing.context.Process object 104471 1 mathieu.dubois-briand 2026-03-03 09:03:27 +0000 a-full fedora43-vk-2 mathieu/master-next completed at 2026-03-02 13:55:15+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/3318/steps/31/logs/stdio 104490 2 mathieu.dubois-briand 2026-03-04 12:12:47 +0000 qa-extras fedora43-vk-2 mathieu/master-next&mathieu/master-next-tests completed at 2026-03-03 12:37:14+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/99/builds/3268/steps/22/logs/stdio 104519 3 randy.macleod 2026-03-05 15:41:06 +0000 Trevor to mark as a duplicate 104522 4 tgamblin 2026-03-05 15:42:28 +0000 Looks like the same bug - need to fix the multiprocessing import. *** This bug has been marked as a duplicate of bug 16184 ***