From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
"Thomas Huth" <thuth@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: 'make check-functional' uses lots of disk space in build tree
Date: Fri, 25 Oct 2024 12:29:13 -0300 [thread overview]
Message-ID: <ac44d70d-2f57-4845-8638-f0939b0c1ea3@linaro.org> (raw)
In-Reply-To: <ZxujrN9bHOboZzZT@redhat.com>
On 25/10/24 10:57, Daniel P. Berrangé wrote:
> 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.
Some files could be added back to the cache (with the proper hash)
so we don't need to re-extract or re-create them everytime.
> 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
next prev parent reply other threads:[~2024-10-25 15:29 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é
2024-10-25 15:29 ` Philippe Mathieu-Daudé [this message]
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=ac44d70d-2f57-4845-8638-f0939b0c1ea3@linaro.org \
--to=philmd@linaro.org \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).