The Unpack shared repositories step fails to copy the poky repo, it isnt able to find the directory: /srv/autobuilder/repos/a-full-2038 It only failed on the beaglebone-alt build (on two different servers, Ubuntu 1604 and Tumbleweed): https://autobuilder.yoctoproject.org/typhoon/#/builders/106/builds/2219 https://autobuilder.yoctoproject.org/typhoon/#/builders/106/builds/2218 Hard to tell why such directory was unavailable at the time, or if it will happen again, but seemed okay to report it. ==================================================================================================== Copying in repo poky (1618170463.3) ==================================================================================================== rsync: [sender] change_dir "/srv/autobuilder/repos/a-full-2038" failed: No such file or directory (2) rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1330) [sender=3.2.3] Traceback (most recent call last): File "/home/pokybuild/yocto-worker/beaglebone-alt/yocto-autobuilder-helper/scripts/shared-repo-unpack", line 57, in <module> subprocess.check_call(["rsync", "-a", "%s/%s" % (args.cache_dir, repo), targetsubdir]) File "/usr/lib64/python3.8/subprocess.py", line 364, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['rsync', '-a', '/srv/autobuilder/repos/a-full-2038/poky', '/home/pokybuild/yocto-worker/beaglebone-alt/build/repos']' returned non-zero exit status 23.
Can be avoided by forcing a build rather than hitting the rebuild button.
Seen again on https://autobuilder.yoctoproject.org/typhoon/#/builders/110/builds/2336/steps/6/logs/stdio qemuarm-alt debian10-ty-3
Issue is from the conditional in http://git.yoctoproject.org/cgit.cgi/yocto-autobuilder-helper/tree/scripts/shared-repo-unpack#n53 When the build completes, the sources are removed as otherwise the can pile up unbounded on the shared storage. One simple fix would be for the code to check if the sources are there and then just checkout sources again if not. The worry is whether a "rebuild" could/would then rebuild something different and confuse the user?
Bulk move from 4.99 or 0.00 to 5.99
We believe the sources cache files are not being deleted which avoids this bug but creates a maintenance issue for cleaning them up