Created attachment 4236 [details] gcc-runtime do_package_write_rpm During an AB run the following error occurred: | DEBUG: Python function write_specfile finished | DEBUG: PKGWRITEDIR: /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-oe-selftest/build/build/tmp/work/core2-64-poky-linux/gcc-runtime/7.3.0-r0/deploy-rpms/core2_64 | DEBUG: SITE files ['endian-little', 'common-linux', 'common-glibc', 'bit-64', 'x86_64-linux', 'common'] | DEBUG: Executing shell function BUILDSPEC | error: failed to create directory %{_builddir}: /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-oe-selftest/build/build/tmp/work-shared/gcc-7.3.0-r0/gcc-7.3.0: File exists | Building target platforms: core2_64-poky-linux | Building for target core2_64-poky-linux It appears that rpmbuild is attempting to create a directory that already exists and doesn't handle it well. Link: https://autobuilder.yocto.io/builders/nightly-oe-selftest/builds/908/steps/Running%20oe-selftest/logs/stdio This occurred in a mut build but I don't see anything in the branch immediately related to this.
Note that this is in shared-workdir and I doubt rpms should be touching a path in work-shared as the _builddir for rpm. This could be gcc-runtime racing against libgcc for packaging. Looking at the logs, "NOTE: recipe libgcc-7.3.0-r0: task do_package_write_rpm: Succeeded" is after the failure so this is very likely the case.
May be worth trying changing the definition of _builddir in package_rpm.bbclass from S to B...
I tried it locally and core-image-sato was able to build and boot, but more testing should probably be done.
Merged in oe-core d6c13a5ff441f7076eb327c0d0b747bd7603db0f.