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/python-fastavro] rawhide: Simplify testing
Date: Sun, 23 Aug 2026 09:57:54 GMT [thread overview]
Message-ID: <178747907472.1.11244223931652096246.rpms-python-fastavro-b79a84af3322@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/python-fastavro
Branch : rawhide
Commit : b79a84af3322dc41ef9d82f3685a245d9cadd7ac
Author : Benjamin A. Beasley <code@musicinmybrain.net>
Date : 2026-08-23T08:34:15+01:00
Stats : +1/-11 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/python-fastavro/c/b79a84af3322dc41ef9d82f3685a245d9cadd7ac?branch=rawhide
Log:
Simplify testing
[skip changelog]
---
diff --git a/python-fastavro.spec b/python-fastavro.spec
index 5f544dd..ec32cbe 100644
--- a/python-fastavro.spec
+++ b/python-fastavro.spec
@@ -136,23 +136,13 @@ install -D --target='%{buildroot}%{_mandir}/man1' \
%check
-# Avoid importing the “un-built” package. The tests really assume we have built
-# the extensions in-place, and occasionally use relative paths to the package
-# source directory. We would prefer to test the extensions as installed (and
-# avoid an extra build step), so we use a symbolic link to make the tests
-# appear alongside the built package.
-mkdir -p _empty
-cd _empty
-cp -rp ../tests/ .
-ln -s '%{buildroot}%{python3_sitearch}/fastavro' .
-
# These fail because there are no source lines in the tracebacks from Cython
# modules, even though this works in the upstream CI. We haven’t figured out
# the root cause, but it doesn’t seem to represent a real problem.
k="${k-}${k+ and }not test_regular_vs_ordered_dict_map_typeerror"
k="${k-}${k+ and }not test_regular_vs_ordered_dict_record_typeerror"
-%pytest -k "${k-}"
+%pytest --import-mode=append -k "${k-}"
%files -n python3-fastavro -f %{pyproject_files}
reply other threads:[~2026-08-23 9:57 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=178747907472.1.11244223931652096246.rpms-python-fastavro-b79a84af3322@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