From: Thomas Huth <thuth@redhat.com>
To: qemu-devel@nongnu.org, "Daniel P. Berrangé" <berrange@redhat.com>
Cc: "John Snow" <jsnow@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: [PATCH 0/2] Clean up the functional download cache after some months
Date: Fri, 10 Oct 2025 11:32:41 +0200 [thread overview]
Message-ID: <20251010093244.807544-1-thuth@redhat.com> (raw)
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.
This little patch series now introduces time stamps for the assets in
the cache (first patch) that we update during each test run, so we can
check these time stamps regularly and evict stale assets after half
of a year not being used anymore (that should be enough time to still
keep the assets around for a while in case you want to diagnose a
problem that is still some months old).
Thomas Huth (2):
tests/functional: Set current time stamp of assets when using them
tests: Evict stale files in the functional download cache after a
while
MAINTAINERS | 1 +
scripts/clean_functional_cache.py | 47 +++++++++++++++++++++++++++++
tests/Makefile.include | 1 +
tests/functional/qemu_test/asset.py | 8 +++++
4 files changed, 57 insertions(+)
create mode 100755 scripts/clean_functional_cache.py
--
2.51.0
next reply other threads:[~2025-10-10 9:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 9:32 Thomas Huth [this message]
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é
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=20251010093244.807544-1-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=jsnow@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
/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).