14393 2021-05-12 02:36:26 +0000 Worker process exited unexpectedly during selftest 2024-03-22 18:05:54 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core unspecified x86 Multiple RESOLVED OBSOLETE AB-INT AB-INT-TMPFS AB-HAVE-PLAN Medium normal 5.0 1 chee.yang.lee richard.purdie alexandre.belloni luca.ceresoli meta.mr.watcher meta.watcher randy.macleod ross.burton --- --- Don't know oldest_to_newest 90348 0 chee.yang.lee 2021-05-12 02:36:26 +0000 https://autobuilder.yoctoproject.org/typhoon/#/builders/86/builds/2081/steps/11/logs/stdio oe-selftest-fedora fedora33-ty-1 NOTE: Running setscene task 21 of 12 (/home/pokybuild/yocto-worker/oe-selftest-fedora/build/bitbake/lib/bb/tests/runqueue-tests/recipes/a1.bb:do_package_write_rpm_setscene) NOTE: Running setscene task 22 of 12 (/home/pokybuild/yocto-worker/oe-selftest-fedora/build/bitbake/lib/bb/tests/runqueue-tests/recipes/a1.bb:do_packagedata_setscene) ERROR: Worker process (1415880) exited unexpectedly (0), shutting down... ERROR: Worker process (1415880) exited unexpectedly (0), shutting down... NOTE: Tasks Summary: Attempted 12 tasks of which 10 didn't need to be rerun and all succeeded. 90389 1 chee.yang.lee 2021-05-14 09:04:24 +0000 https://autobuilder.yoctoproject.org/typhoon/#/builders/108/builds/1644/steps/12/logs/stdio qemux86-world-alt centos7-ty-4 90833 2 richard.purdie 2021-07-01 22:01:31 +0000 Second failure is exit -9 - EBADF. First failure is exit 0. Maybe a race in the shutdown code somehow? 91440 3 richard.purdie 2021-09-16 11:59:16 +0000 I think the first failure was some kind of fault in bitbake-worker. The real failure was probably in the bitbake-cookerdaemon.log but long gone now. I've added a fix to bitbake to ensure we don't see the "exit 0" success code if there is a fault: http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=4437754142f6d0e8f3cf9ffbb51c61321b8c5600 I think the second failure was the OOM killer in action with SIGKILL being the sig 9. Not much to be done about that. Closing, if we see this again we need the bitbake-cookerdaemon log to get any further and hopefully we won't see the exit 0 again. 93875 4 luca.ceresoli 2022-08-23 10:40:51 +0000 https://autobuilder.yoctoproject.org/typhoon/#/builders/86/builds/3988/steps/11/logs/stdio oe-selftest-fedora on fedora36-ty-3 bitbake-cookerdaemon.log and dmesg did not seem to contain useful clues. 93882 5 richard.purdie 2022-08-23 15:38:18 +0000 At least this time upon recurrence it did show exit 1 instead of 0 so we have some idea which code paths were triggering, but still no cooker log :( 94396 6 ross.burton 2022-11-10 15:45:40 +0000 I saw this earlier in the week, so it's not disappeared... 95190 7 randy.macleod 2023-03-23 14:59:10 +0000 Likely still a problem so keeping it opened even though it hasn't happened in months. 98595 8 richard.purdie 2024-03-22 18:05:54 +0000 We've not logged this in a long time, closing and can reopen if it reappears. Assuming there were other fixes which stopped it happening.