Closed kloczek closed 1 year ago
pytest automatically tries to scan test/test_ files. Those .txt files should be renamed to be able use pytest. After pass `test/.py` files as pytest param:
Looks like test suite is not ready to be used with pytest 😞
run pytest with $PYTHONPATH pointing to sitearch and sitelib inside </install/prefix>
Please run python test/runtests.py
instead. The test suite only partially was converted to the pytest framework, see #377. Let us know if you still will be observe test failures.
Looks like test suite is not ready to be used with pytest
Yep.
Thank you. I've subscribed to that ticket 👍 As in my distribution I'm trying to test everything using pytest I'll keep current test procedure .. even if it temporary/partially fails. As you already mention that moving to pytest is in kind of WIP state for long term reason IMO better will be if I'll stick with pytest even if it fails temporary 😋 Using pytest allows me to perform many additional variants of the tests by install additional pytest extensions in build env.
As in my distribution I'm trying to test everything using pytest I'll keep current test procedure .. even if it temporary/partially fails.
Whatever you wish, but if you are unable to reproduce test failures with a correct invocation of the gmpy2 test suite (as described above) - I believe this issue should be closed.
If you are going to continue migration to pytest under that ticket which you mention I think that you are right. I'm not sure so I'm leaving you decision 😋
How do you suggest to fix this issue?
My understanding is that your intention is to move test suite from custom framework to pytest and that work is in WIP state so fixing this issue may take longer time and/or is not critical as non-pytest based test suite runner is working.
If that is true I was ot aware of that and as work on pytest migration is done under different ticket probably this ticket can be closed. As I've already found that that I was not aware some development details as I wrote I'm leaving you you decision about closing or not this ticket .. only this an nothing more.
@casevh, I think this can be closed.
Closing.
I'm packaging 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 modulescut off from access to the public network
(pytest is executed with-m "not network"
)I'm using gmp 6.2.1 and mpfr 4.2.1. Here is pytest output:
Here is list of installed modules in build env