From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>, Thomas Huth <thuth@redhat.com>
Subject: Re: 'make check-functional' uses lots of disk space in build tree
Date: Fri, 25 Oct 2024 14:57:00 +0100 [thread overview]
Message-ID: <ZxujrN9bHOboZzZT@redhat.com> (raw)
In-Reply-To: <CAFEAcA8DE=i5X_=GxqrupOMqrQ6-BoL2HWo_GPe1pNhL15QU5g@mail.gmail.com>
On Fri, Oct 25, 2024 at 02:50:50PM +0100, Peter Maydell wrote:
> I notice that with the recent migration to check-functional we
> seem to be using a lot of disk space in the build tree: for
> one of my build trees
> du -h build/arm-clang/tests/functional/
> returns a total of 4.5GB used, for instance, most of which seems
> to be guest binary files.
>
> Shouldn't something be cleaning these up after a test run?
The big problem seems to be tests/functional/test_aarch64_sbsaref.py
which is creating a pair of 256 MB firmware files on every test
and not deleting them.
The tests/functional/test_arm_raspi2.py is also uncompressing some
archives and not deleting them.
Perhaps we need to define a standard "scratch dir" in the framework
that files can be put into, and then have the framework force delete
them at the end.
With 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 :|
next prev parent reply other threads:[~2024-10-25 13:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 13:50 'make check-functional' uses lots of disk space in build tree Peter Maydell
2024-10-25 13:57 ` Daniel P. Berrangé [this message]
2024-10-25 15:29 ` Philippe Mathieu-Daudé
2024-10-25 15:50 ` Daniel P. Berrangé
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZxujrN9bHOboZzZT@redhat.com \
--to=berrange@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.