ctest mistake

[wangylx20150815]

[root@bogon installer]# cat configureYDWCPU

#load the module for cmake
export LBPM_SOURCE="/soft/ops/LBPM-slim-master/"
export LBPM_DIR="/usr/local/lbpm"

mkdir $LBPM_DIR
cd $LBPM_DIR

configure

rm -rf CMake*
cmake
-D CMAKE_BUILD_TYPE:STRING=Release
-D CMAKE_CXX_COMPILER:PATH=mpicxx
-D USE_MPI=1
$LBPM_SOURCE
make -j32 && make install && ctest

The following tests FAILED:
1 - TestFluxBC (Failed)
2 - TestMap (Failed)
3 - TestColorGradDFH (Failed)
4 - TestPressVel--../example/Bubble/input.db (Failed)
5 - TestPoiseuille--../example/Piston/poiseuille.db (Failed)
6 - TestForceMoments--../example/Bubble/input.db (Failed)
9 - TestMassConservationD3Q7--../example/Bubble/input.db (Failed)
10 - TestSegDist_8procs (Failed)
11 - TestCommD3Q19_8procs (Failed)
21 - TestColorBubble--../example/Bubble/input.db (Failed)
22 - TestColorSquareTube--../example/Bubble/input.db (Failed)
Errors while running CTest

[JamesEMcClure]

When building for a CPU based system, you may need to specify the name of the launch command by adding a line such as the following

-D MPIEXEC=mpirun \

See below for an example
https://github.com/OPM/LBPM/blob/master/sample_scripts/configure_cascades_cpu

For GPU applications it is more complicated, because the launch command may also need additional flags / arguments to specify how to launch the application within your environment. This often depends on the MPI implementation (e.g openmpi or mvapich2), how the MPI implementation was compiled, and on other factors (such as if a scheduler like slurm is being used as the launcher).