You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would first question what is make test supposed to test. If you run it inside the build environment it does not pick up the post installation files (e.g. the python files), and by the time you make it work without it, you end up being able to simply run ctest without scikit-build-core. If you run it outside than you can simply run pip install -e and then do some standard pytest.
My approach is to have both a ctest and a pytest runner that complement each other, rather than trying to maneuver around having everything in one.
I would second that, if you have pure compiled tests, you should probably build outside of scikit-build-core and run those tests. You should also have pytest tests that run with the installed package.
But yes, what you are describing is actually a build target named test, and we support specifying build targets.
I'm attempting to make use of scikit build core on openmc which currently has a two stage build process (
cmake
andpip
)Currently in the CI the package is build with
cmake ..
then tested withmake test
Is there a way of running the equivalent of this make test command when the package has been built with scikit build core?
The text was updated successfully, but these errors were encountered: