public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Benjamin A. Beasley <code@musicinmybrain.net>
To: git-commits@fedoraproject.org
Subject: [rpms/uv] rawhide: Skip some tests related to managed interpreters on riscv64
Date: Fri, 24 Jul 2026 07:16:01 GMT	[thread overview]
Message-ID: <178487736179.1.16080706139006534231.rpms-uv-97c5cc15eec2@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/uv
Branch : rawhide
Commit : 97c5cc15eec2ba5cde5fbebeb4bfceb3b1440ce1
Author : Benjamin A. Beasley <code@musicinmybrain.net>
Date   : 2026-07-24T08:14:59+01:00
Stats  : +10/-0 in 1 file(s)
URL    : https://src.fedoraproject.org/rpms/uv/c/97c5cc15eec2ba5cde5fbebeb4bfceb3b1440ce1?branch=rawhide

Log:
Skip some tests related to managed interpreters on riscv64

---
diff --git a/uv.spec b/uv.spec
index 331ca44..19e1c77 100644
--- a/uv.spec
+++ b/uv.spec
@@ -615,6 +615,16 @@ skip="${skip-} --skip python_list::python_list_with_mirrors"
 # This might be worth reporting upstream, but is not a serious issue.
 skip="${skip-} --skip python_pin::python_pin_resolve"
 %endif
+%ifarch riscv64
+# These expect managed interpreters of the form
+# cpython-3.##-linux-riscv64gc-any, but crates/uv-python/download-metadata.json
+# only has them for cpython-3.##-linux-riscv64-gnu. It’s not weird to find
+# holes in the managed interpreter support matrix for less common
+# architectures.
+skip="${skip-} --skip python_find::python_find"
+skip="${skip-} --skip python_list::python_list"
+skip="${skip-} --skip python_pin::python_pin_resolve"
+%endif
 # Test registry_client::tests::test_redirect_to_server_with_credentials is
 # flaky
 # https://github.com/astral-sh/uv/issues/16447

                 reply	other threads:[~2026-07-24  7:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=178487736179.1.16080706139006534231.rpms-uv-97c5cc15eec2@fedoraproject.org \
    --to=code@musicinmybrain.net \
    --cc=git-commits@fedoraproject.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