Closed kloczek closed 2 years ago
expected failure
Does it mean that it know bug, or some kind feature which needs some adaptation in other modules? 🤔
its a known breakage - pylib wl not adopt to be testable on modern pytest, its going to be phased out
OK now it is clear. Thx 😄
This issue is now affecting probably +10 other modules test suite. Ronny may I ask you tall few words what needa to be done to get rid of that and/or is irt any working solution for that issue? Did I push some updates in my packaged modules to far? 🤔
Basically someone would have to forward port the testsuite of pylib to use modern fixtures instead of the initial fixture mechanism,
Currently I'm not aware of anyone wanting to work on that
Im also unlikely to Touch this in a meaningful way anytime soon
As pytest is preparing to completely shed itself from pylib in the mid term future, it's likely that a fix won't happen as it's currently looking like a painful amount of thankless and low value wortk
I understand the pain of not being able to verify a dependency
I don't understand how pylib's selftests failing would affect other projects.
There are more than few modules affected by that issue.
Just found for example that on update unicoirn
to 0.17.1 pytest is failing with the same internal error 😞
I doubt unicorn uses an internal conftest.py from pylib's selftest. You are likely looking at a different error.
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 oly locally installed modulesHere is pytest output: