From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org, "John Snow" <jsnow@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH 2/2] tests: Evict stale files in the functional download cache after a while
Date: Mon, 13 Oct 2025 12:50:35 +0100 [thread overview]
Message-ID: <aOzni0KXA9nysxUA@redhat.com> (raw)
In-Reply-To: <2cc78a29-6df7-4cfa-86b8-6065869a8a85@redhat.com>
On Mon, Oct 13, 2025 at 01:47:57PM +0200, Thomas Huth wrote:
> On 10/10/2025 11.50, Daniel P. Berrangé wrote:
> > On Fri, Oct 10, 2025 at 11:32:43AM +0200, Thomas Huth wrote:
> > > From: Thomas Huth <thuth@redhat.com>
> > >
> > > The download cache of the functional tests is currently only growing.
> > > But sometimes tests get removed or changed to use different assets,
> > > thus we should clean up the stale old assets after a while when they
> > > are not in use anymore. So add a script that looks at the time stamps
> > > of the assets and removes them if they haven't been touched for more
> > > than half of a year. Since there might also be some assets around that
> > > have been added to the cache before we added the time stamp files,
> > > assume a default time stamp that is close to the creation date of this
> > > patch, so that we don't delete these files too early.
> > >
> > > Signed-off-by: Thomas Huth <thuth@redhat.com>
> > > ---
> > > MAINTAINERS | 1 +
> > > scripts/clean_functional_cache.py | 47 +++++++++++++++++++++++++++++++
> > > tests/Makefile.include | 1 +
> > > 3 files changed, 49 insertions(+)
> > > create mode 100755 scripts/clean_functional_cache.py
> > >
> > > diff --git a/MAINTAINERS b/MAINTAINERS
> > > index 84cfd85e1fa..4c468d45337 100644
> > > --- a/MAINTAINERS
> > > +++ b/MAINTAINERS
> > > @@ -4398,6 +4398,7 @@ M: Thomas Huth <thuth@redhat.com>
> > > R: Philippe Mathieu-Daudé <philmd@linaro.org>
> > > R: Daniel P. Berrange <berrange@redhat.com>
> > > F: docs/devel/testing/functional.rst
> > > +F: scripts/clean_functional_cache.py
> > > F: tests/functional/qemu_test/
> > > Windows Hosted Continuous Integration
> > > diff --git a/scripts/clean_functional_cache.py b/scripts/clean_functional_cache.py
> > > new file mode 100755
> > > index 00000000000..e5c4d1acaf3
> > > --- /dev/null
> > > +++ b/scripts/clean_functional_cache.py
> > > @@ -0,0 +1,47 @@
> > > +#!/usr/bin/env python3
> > > +#
> > > +# SPDX-License-Identifier: GPL-2.0-or-later
> > > +#
> > > +"""Delete stale assets from the download cache of the functional tests"""
> > > +
> > > +import os
> > > +import stat
> > > +import sys
> > > +import time
> > > +from pathlib import Path
> > > +
> > > +
> > > +cache_dir_env = os.getenv('QEMU_TEST_CACHE_DIR')
> > > +if cache_dir_env:
> > > + cache_dir = Path(cache_dir_env, "download")
> > > +else:
> > > + cache_dir = Path(Path("~").expanduser(), ".cache", "qemu", "download")
> >
> > This creates a Path object but then doesn't take advantage of
> > any of its functionality, calling os. functions still....
>
> Ok, you got me, looks like I'm still a python ignorant after one year of
> hacking the functional testing framework ;-) Thanks for the hints how to do
> it better!
>
> > > + try:
> > > + with open(filename + ".stamp", "r", encoding='utf-8') as fh:
> > > + timestamp = int(fh.read())
> >
> > timestamp = file.read_text()
>
> Hmm, but "file" points to the asset, not to the .stamp file, doesn't it?
Opps, yes, you'll need
file.with_stem(".stamp").read_text()
> > > + except FileNotFoundError:
> > > + # Assume it's an old file that was already in the cache before we
> > > + # added the code for evicting stale assets. Use the release date
> > > + # of QEMU v10.1 as a default timestamp.
> > > + timestamp = time.mktime((2025, 8, 26, 0, 0, 0, 0, 0, 0))
> >
> > The prev patch will make the precache task create the .stamp for all
> > files that are currently in use by the current branch. So the only
> > thing this does is to prevent us deleting cached files that might
> > still be needed by a different branch. There will be few of them,
> > so if we prematurely delete a handful that's not a big deal. If we
> > switch to checking mtime, this except won't even exist.
>
> When hunting regressions that have been introduced recently, I often have to
> do bisecting on revisions from the previous 1 or 2 QEMU releases, so I'd
> prefer keeping the assets of the last few months, even if they have been
> removed from the master branch in a very recent commit.
Ok.
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 :|
prev parent reply other threads:[~2025-10-13 11:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 9:32 [PATCH 0/2] Clean up the functional download cache after some months Thomas Huth
2025-10-10 9:32 ` [PATCH 1/2] tests/functional: Set current time stamp of assets when using them Thomas Huth
2025-10-10 9:39 ` Daniel P. Berrangé
2025-10-10 9:46 ` Thomas Huth
2025-10-10 9:53 ` Daniel P. Berrangé
2025-10-10 9:32 ` [PATCH 2/2] tests: Evict stale files in the functional download cache after a while Thomas Huth
2025-10-10 9:50 ` Daniel P. Berrangé
2025-10-13 11:47 ` Thomas Huth
2025-10-13 11: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=aOzni0KXA9nysxUA@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=jsnow@redhat.com \
--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 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).