All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: Thomas Huth <thuth@redhat.com>,
	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 16:50:42 +0100	[thread overview]
Message-ID: <Zxu-UlT2nvreKvBT@redhat.com> (raw)
In-Reply-To: <ac44d70d-2f57-4845-8638-f0939b0c1ea3@linaro.org>

On Fri, Oct 25, 2024 at 12:29:13PM -0300, Philippe Mathieu-Daudé wrote:
> 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.

Unless we've seen a significant time penalty from the extraction,
I think we shouldn't complicate our cache handling. Simplicity
is of great value when it comes to debugging problems with tests.

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 :|



      reply	other threads:[~2024-10-25 15:51 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é
2024-10-25 15:50     ` Daniel P. Berrangé [this message]

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=Zxu-UlT2nvreKvBT@redhat.com \
    --to=berrange@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@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.