On Fri, Aug 17, 2018 at 11:26:39AM +0100, Peter Maydell wrote: > I just ran into a build failure using the tests/vm/ BSD build tests, > because the NetBSD build image's disk filled up. > > Looking more closely there seemed to be 9 stale build trees in > the VM's /var/tmp/qemu-test.* , which is why the disk was full > (they'd used up about 18GB between them). > > The other VMs (freebsd, openbsd) also had the same problem of > /var/tmp gradually filling with stale trees, they just hadn't > quite run out of space yet... > > What's the process for managing the disk space on these images? > How are stale or completed build trees deleted ?
I'd prefer to see the test process honouring the build directory instead of putting stuff in /var/tmp, so that a developer's normal approach to cleaning up build artifacts works. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|