Tonight's run on the AB appears to have ran out of space in /tmp, but the /tmp-is-full detection didn't trigger: https://autobuilder.yoctoproject.org/main/builders/nightly-arm64/builds/49/steps/BuildImages/logs/stdio
Looks like writing 1KB isn't enough: Filesystem Size Used Avail Use% Mounted on /dev/dm-0 9.1G 8.6G 4.0K 100% / We should probably write a block worth of data. Block size can be fetching using statvfs (stat -f -c %s /tmp) from the shell, python has os.statvfs IIRC)
Better idea - rip the test out and use the disk monitoring support instead. Totally forgot that existed... From local.conf: # # Disk Space Monitoring during the build # # Monitor the disk space during the build. If there is less that 1GB of space or less # than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully # shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort # of the build. The reason for this is that running completely out of space can corrupt # files and damages the build in ways which may not be easily recoverable. BB_DISKMON_DIRS = "\ STOPTASKS,${TMPDIR},1G,100K \ STOPTASKS,${DL_DIR},1G,100K \ STOPTASKS,${SSTATE_DIR},1G,100K \ ABORT,${TMPDIR},100M,1K \ ABORT,${DL_DIR},100M,1K \ ABORT,${SSTATE_DIR},100M,1K" Adding a pair of entries for /tmp (100mb/10mb?) seems like a sensible solution.
Sent patches for review
This bug has been fixed with commits: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=9f87dcf3a3adf0b215b59eac854d372216c9dc0d http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=0a5f2bc3e2e2f8538e1c3e6602ecb90139e821d0
verified on master db92bc23880794be77373b0f2d8c26279dcecb84; I modified the values here BB_DISKMON_DIRS - "ABORT,/tmp,2000M,700K" in order to exceed the values on my machine (tmpfs 1.9G 352K 1.9G 1% /tmp); Space monitoring detected: WARNING: The free inode of /tmp (tmpfs) is running low (479.841K left) ERROR: Immediately abort since the disk space monitor action is "ABORT"! WARNING: The free space of /tmp (tmpfs) is running low (1.874GB left) ERROR: Immediately abort since the disk space monitor action is "ABORT"!