Closed kloczek closed 1 year ago
Coconut's test suite is not meant to be invoked outside of the context of Coconut's continuous integration tests. The test suite is very complex, takes an extremely long time to run, and has dependencies outside of the normal Coconut dependencies, such that maintaining it in such a way to guarantee that it succeeds when built on arbitrary platforms is not something that I can do.
If you want to run some tests to verify that your installation is working, I'd recommend instead mimicking what make test-univ
does and running something like:
python ./coconut/tests
python ./coconut/tests/dest/runner.py
python ./coconut/tests/dest/extras.py
How long it taked and much it is complicated it really doesn't matter. So what is wrong with those units and what kind of external dependencies test suite has? 🤔 I'm trying to test all my packages with python modules usig pytest because it provides for many many other possibilies to perform other types of tests without touching build procedure described in rpm spec file by only altering list of modules instaled in build env. In other words using anything else than pytest is not good option 😞
In udated build env I see now more units failing Here is pytest output:
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"
)Here is pytest output:
Here is list of installed modules in build env