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/maturin] rawhide: Skip a test that requires a particular locked PyO3 version
Date: Tue, 04 Aug 2026 13:33:00 GMT	[thread overview]
Message-ID: <178585038033.1.11757405256287095689.rpms-maturin-af5a001bffeb@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/maturin
Branch : rawhide
Commit : af5a001bffeb9b5b8cf46a4a0e3123edf80c633f
Author : Benjamin A. Beasley <code@musicinmybrain.net>
Date   : 2026-08-04T13:52:58+01:00
Stats  : +8/-0 in 1 file(s)
URL    : https://src.fedoraproject.org/rpms/maturin/c/af5a001bffeb9b5b8cf46a4a0e3123edf80c633f?branch=rawhide

Log:
Skip a test that requires a particular locked PyO3 version

---
diff --git a/maturin.spec b/maturin.spec
index 837fe77..4d21afd 100644
--- a/maturin.spec
+++ b/maturin.spec
@@ -229,6 +229,14 @@ skip="${skip-} --skip=integration::pyo3_cffi_build_script"
 skip="${skip-} --skip=pep517::pep517_default_profile"
 skip="${skip-} --skip=pep517::pep517_editable_profile"
 
+# This relies on a hard-coded PyO3 version number, which needs to match the one
+# in test-crates/pyo3-pure/Cargo.lock. This is correct upstream as long as the
+# two versions are kept synchronized; it doesn’t work downstream where we use
+# system-packaged crates to build test crates, and we don’t respect the
+# Cargo.lock files. Since only this test relies on a particular patch version
+# specified in the upstream lock files, it’s best to simpl skip it.
+skip="${skip-} --skip=build_options::tests::test_find_bridge_pyo3_abi3"
+
 # Don’t attempt WASM-related tests.
 # (“Failed to build a native library through cargo”)
 skip="${skip-} --skip=integration::integration_wasm_hello_world"

                 reply	other threads:[~2026-08-04 13:33 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=178585038033.1.11757405256287095689.rpms-maturin-af5a001bffeb@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