Closed kloczek closed 2 years ago
Looks to me like pytest-asyncio
doesn't run warnings-clean, so you'll need to do the build without that package installed.
Looks like the issue can be solved by patch
--- a/pytest.ini~ 2022-03-29 04:01:46.000000000 +0000
+++ b/pytest.ini 2022-03-29 18:59:13.691793577 +0000
@@ -1,4 +1,5 @@
[pytest]
+asyncio_mode = auto
# -rfEX :: Print a summary of failures, errors, and xpasses (xfails that pass).
addopts=--strict-markers --tb=native -p pytester --runpytest=subprocess --durations=20 -rfEX
``
We don't accept patches to run our self-tests outside our own test environments, but that does look like a sensible downstream solution 👍
I'm trying to package your module as an rpm package. So I'm using the typical PEP517 based build, install and test cycle used on building packages from non-root account.
python3 -sBm build -w --no-isolation
build
with--no-isolation
I'm using during all processes only locally installed modulesHere is pytest output in which are some call traces and warnings: