PyTest usage is broken

[Vijay M]

pytest workflows are completely broken. When building PyMOAB with CMake, make test runs fine and successfully verifies that all python tests are launched and executed correctly. However, pytest -ra is completely broken.

I thought I had tested this change on my linux box before approving/merging the PR. But now, I can’t replicate a successful behavior anywhere. Bitbucket pipelines and my local MacBook are failing as well. So we should either revert the pytest change, or update this correctly.

___________________________________________________________________ ERROR collecting test/pymoab/pymoab/test_core.py ____________________________________________________________________
ImportError while importing test module '/nfs/gce/projects/sigma/vijaysm/moab/build/cmake/test/pymoab/pymoab/test_core.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3.10/importlib/__init__.py:126: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
test/pymoab/pymoab/test_core.py:1: in <module>
    from pymoab import core
E   ModuleNotFoundError: No module named 'pymoab'

‌

[Vijay M]

@Ahnaf Tahmid Chowdhury @pshriwise @gonuke Is this being tested elsewhere? We are preparing for a release and some CI systems are now broken. The wheel install and subsequent pytest does not find valid modules. If you have a working build, please update with instructions.

[Ahnaf Tahmid Chowdhury]

I've fixed the issue in PR #690. I realized that I had written the code for building the wheel but forgot to include the installation step. I've added that now, and I believe it should work as expected.