All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: qemu-devel@nongnu.org, "Daniel P. Berrangé" <berrange@redhat.com>
Cc: "John Snow" <jsnow@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: [PATCH] scripts: Allow sha512 in clean_functional_cache.py, too
Date: Tue, 20 Jan 2026 13:18:49 +0100	[thread overview]
Message-ID: <20260120121849.131604-1-thuth@redhat.com> (raw)

From: Thomas Huth <thuth@redhat.com>

The functional testing frameworks also supports assets that are
identified by their sha512 checksum (instead of only using sha25),
and at least one of the tests (tests/functional/ppc64/test_fadump.py)
is already using such a checksum, so adjust the clean_functional_cache
script to support these checksums, too.

Signed-off-by: Thomas Huth <thuth@redhat.com>
---
 scripts/clean_functional_cache.py | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/scripts/clean_functional_cache.py b/scripts/clean_functional_cache.py
index c3370ffbb87..f0342b4b438 100755
--- a/scripts/clean_functional_cache.py
+++ b/scripts/clean_functional_cache.py
@@ -24,8 +24,8 @@
 os.chdir(cache_dir)
 
 for file in cache_dir.iterdir():
-    # Only consider the files that use a sha256 as filename:
-    if len(file.name) != 64:
+    # Only consider the files that use a sha256 or sha512 as filename:
+    if len(file.name) != 64 and len(file.name) != 128:
         continue
 
     try:
-- 
2.52.0



             reply	other threads:[~2026-01-20 12:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-20 12:18 Thomas Huth [this message]
2026-01-20 13:02 ` [PATCH] scripts: Allow sha512 in clean_functional_cache.py, too Daniel P. Berrangé
2026-01-20 14:10   ` Thomas Huth
2026-01-20 14:44     ` 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=20260120121849.131604-1-thuth@redhat.com \
    --to=thuth@redhat.com \
    --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 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.