-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adjusting test cases from mock tests to proper tests for testZfpCuda4d<datatype>
#235
Comments
@JanLJL Thanks for your contribution. Let me begin by pointing out that we're in the midst of making significant changes to the CUDA (and HIP) implementation on the I should also point out that the work on Regarding testing, which should not be impacted at all by the work being done on zfp/tests/src/endtoend/cudaExecBase.c Lines 157 to 163 in 5c976d8
You'll also need changes here:
There are also dimension-specific source files Some of the test code has been written to be dimension and execution policy independent, so hopefully adding proper 4D CUDA tests could be done fairly painlessly. But it's been long enough since I worked on those tests that I'm not sure how much effort is involved. There's also a new testexec test on |
Hi Peter, |
I'm hoping to push some more recent work but am reluctant to do so until the code compiles and runs. Currently, the code is in a broken state, which is not very helpful to you. I'm hoping to get to that point in the next couple of weeks. |
Hi,
I enhanced ZFP to also support 4D arrays for CUDA and would like to open a PR soon to merge this into the main project.
However, I see when running the tests (built with
-DBUILD_TESTING_FULL=ON
) that for the 4D case, the test suite seems to run mock tests for the CUDA 4D cases and assert0x0
due to the fact this functionality wasn't implemented previously.I don't have much experience with GoogleTest and find the whole structure of the tests a bit confusing, can you point me to the right files/lines of code I have to adjust so the tests are testing against the actual checksum?
Thanks and best,
Jan
The text was updated successfully, but these errors were encountered: