Repository navigation
Avoid requiring editable builds (-e) for running tests #108
Description
Right now it is quite subtle that the test/benchmark suites are designed to only allow editable builds to run. For normal builds, pytest has a hard time importing the needed modules. I stumbled over this for a few times.
cuda-python/docs_src/source/install.md
Line 65 in e1e3325
This should be fixed.
Activity
leofang commentedon Oct 10, 2024
Not sure if this is related, but instead of the current layout for tests/examples/benchmarks
ideally the layout should have been made such that they are outside of source tree and living side-by-side with
setup.pyfor the package, soI probably made a bad mistake back then (leofang#1) 😓
cc @vzhurba01
Apply remaining touch ups for patch release
Apply remaining touch ups for patch release
vzhurba01 commentedon Oct 11, 2024
Resolved by MR #159. Updated cuda-python/cuda/README.md with how to run.
The final commands are:
Command to test against in-tree builds:
cuda-python/cuda_bindings$ python -m pytest tests/cuda-python/cuda_bindings$ python -m pytest examples/Command to test against distributable package (wheels/conda)
cuda-python/cuda_bindings$ pytest tests/cuda-python/cuda_bindings$ pytest examples/Closing.