Currently the only test in ports-of-call is the install test. This PR does a minimal build configuration for inline tests.
I have included a test from spiner that tests PortableMDArray, but that is just so there is something to test. It appears there are several tests in spiner that should properly be in ports-of-call.
New CMake options:
-DBUILD_TESTING=[ON/OFF] for triggering the build of the test exe(s)
-DPORTS_OF_CALL_TEST_KOKKOS=[ON/OFF] for configuring for testing with Kokkos
Dependencies
I'm taking a "less-is-more" approach here; if you want to test, you need Catch2 available - diddo with Kokkos. Further, I've deliberately left out an option for Kokkos CUDA; If you want that, then install Kokkos with CUDA enabled.
CI ?
Should the git[hub/lab] CI begin running these tests? Or should that be a separate PR?
PR Checklist
[ ] Any changes to code are appropriately documented.
[ ] Code is formatted.
[ ] Install test passes.
[ ] Docs build.
[ ] If preparing for a new release, update the version in cmake.
PR Summary
Currently the only test in
ports-of-call
is the install test. This PR does a minimal build configuration for inline tests.I have included a test from
spiner
that testsPortableMDArray
, but that is just so there is something to test. It appears there are several tests inspiner
that should properly be inports-of-call
.New CMake options:
-DBUILD_TESTING=[ON/OFF]
for triggering the build of the test exe(s)-DPORTS_OF_CALL_TEST_KOKKOS=[ON/OFF]
for configuring for testing withKokkos
Dependencies
I'm taking a "less-is-more" approach here; if you want to test, you need
Catch2
available - diddo withKokkos
. Further, I've deliberately left out an option for Kokkos CUDA; If you want that, then install Kokkos with CUDA enabled.CI ?
Should the git[hub/lab] CI begin running these tests? Or should that be a separate PR?
PR Checklist