Skip to content
Snippets Groups Projects
Commit 8d0e1dc7 authored by Stéphane Del Pino's avatar Stéphane Del Pino
Browse files

Set OptionalCatchTestLauncher when testing with MPI

Now test names are deduced similarly to sequential unit tests

Fixes #2
parent 9cf6f477
Branches
Tags
1 merge request!11Feature/mpi
...@@ -40,14 +40,7 @@ enable_testing() ...@@ -40,14 +40,7 @@ enable_testing()
ParseAndAddCatchTests(unit_tests) ParseAndAddCatchTests(unit_tests)
if(${PASTIS_HAS_MPI}) if(${PASTIS_HAS_MPI})
add_test(mpi_unit_tests ${MPIEXEC} ${MPIEXEC_NUMPROC_FLAG} 3 "--oversubscribe" set(OptionalCatchTestLauncher ${MPIEXEC} ${MPIEXEC_NUMPROC_FLAG} 3 --oversubscribe --path ${PASTIS_BINARY_DIR})
${MPIEXEC_PREFLAGS}
${PASTIS_BINARY_DIR}/mpi_unit_tests
${MPIEXEC_POSTFLAGS})
else()
add_test(mpi_unit_tests ${PASTIS_BINARY_DIR}/mpi_unit_tests)
endif() endif()
ParseAndAddCatchTests(mpi_unit_tests)
# Should patch ParseAndAddCatchTests macro to allow additional command parameter unset(OptionalCatchTestLauncher)
# to launch tests
set_tests_properties("mpi_unit_tests" PROPERTIES FAIL_REGULAR_EXPRESSION "No tests ran" LABELS "mpi")
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment