Start testing: Aug 06 23:28 PDT ---------------------------------------------------------- 1/27 Testing: precice.acceleration 1/27 Test: precice.acceleration Command: "/usr/local/bin/mpiexec" "-n" "4" "/Users/siqiwei/precice-2.1.0/build/testprecice" "--run_test=AccelerationTests" Directory: /Users/siqiwei/precice-2.1.0/build/TestOutput/acceleration "precice.acceleration" start time: Aug 06 23:28 PDT Output: ---------------------------------------------------------- This test suite runs on rank 1 of 4 This test suite runs on rank 3 of 4 This test suite runs on rank 2 of 4 This test suite runs on rank 0 of 4 Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level -------------------------------------------------------------------------- Primary job terminated normally, but 1 process returned a non-zero exit code. Per user-direction, the job has been aborted. -------------------------------------------------------------------------- -------------------------------------------------------------------------- mpiexec detected that one or more processes exited with non-zero status, thus causing the job to be terminated. The first process to do so was: Process name: [[58024,1],0] Exit code: 200 -------------------------------------------------------------------------- Test time = 2.37 sec ---------------------------------------------------------- Test Failed. "precice.acceleration" end time: Aug 06 23:28 PDT "precice.acceleration" time elapsed: 00:00:02 ---------------------------------------------------------- 2/27 Testing: precice.action 2/27 Test: precice.action Command: "/usr/local/bin/mpiexec" "-n" "4" "/Users/siqiwei/precice-2.1.0/build/testprecice" "--run_test=ActionTests" Directory: /Users/siqiwei/precice-2.1.0/build/TestOutput/action "precice.action" start time: Aug 06 23:28 PDT Output: ---------------------------------------------------------- This test suite runs on rank 0 of 4 This test suite runs on rank 1 of 4 This test suite runs on rank 3 of 4 This test suite runs on rank 2 of 4 Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level -------------------------------------------------------------------------- Primary job terminated normally, but 1 process returned a non-zero exit code. Per user-direction, the job has been aborted. -------------------------------------------------------------------------- -------------------------------------------------------------------------- mpiexec detected that one or more processes exited with non-zero status, thus causing the job to be terminated. The first process to do so was: Process name: [[58029,1],0] Exit code: 200 -------------------------------------------------------------------------- Test time = 2.27 sec ---------------------------------------------------------- Test Failed. "precice.action" end time: Aug 06 23:28 PDT "precice.action" time elapsed: 00:00:02 ---------------------------------------------------------- 3/27 Testing: precice.com 3/27 Test: precice.com Command: "/usr/local/bin/mpiexec" "-n" "4" "/Users/siqiwei/precice-2.1.0/build/testprecice" "--run_test=CommunicationTests:!CommunicationTests/MPIPorts:!CommunicationTests/MPISinglePorts" Directory: /Users/siqiwei/precice-2.1.0/build/TestOutput/com "precice.com" start time: Aug 06 23:28 PDT Output: ---------------------------------------------------------- This test suite runs on rank 1 of 4 This test suite runs on rank 2 of 4 This test suite runs on rank 3 of 4 This test suite runs on rank 0 of 4 Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level -------------------------------------------------------------------------- Primary job terminated normally, but 1 process returned a non-zero exit code. Per user-direction, the job has been aborted. -------------------------------------------------------------------------- -------------------------------------------------------------------------- mpiexec detected that one or more processes exited with non-zero status, thus causing the job to be terminated. The first process to do so was: Process name: [[58018,1],0] Exit code: 200 -------------------------------------------------------------------------- Test time = 2.26 sec ---------------------------------------------------------- Test Failed. "precice.com" end time: Aug 06 23:28 PDT "precice.com" time elapsed: 00:00:02 ---------------------------------------------------------- 4/27 Testing: precice.cplscheme 4/27 Test: precice.cplscheme Command: "/usr/local/bin/mpiexec" "-n" "4" "/Users/siqiwei/precice-2.1.0/build/testprecice" "--run_test=CplSchemeTests" Directory: /Users/siqiwei/precice-2.1.0/build/TestOutput/cplscheme "precice.cplscheme" start time: Aug 06 23:28 PDT Output: ---------------------------------------------------------- This test suite runs on rank 0 of 4 This test suite runs on rank 2 of 4 This test suite runs on rank 3 of 4 This test suite runs on rank 1 of 4 Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level -------------------------------------------------------------------------- Primary job terminated normally, but 1 process returned a non-zero exit code. Per user-direction, the job has been aborted. -------------------------------------------------------------------------- -------------------------------------------------------------------------- mpiexec detected that one or more processes exited with non-zero status, thus causing the job to be terminated. The first process to do so was: Process name: [[58023,1],0] Exit code: 200 -------------------------------------------------------------------------- Test time = 2.27 sec ---------------------------------------------------------- Test Failed. "precice.cplscheme" end time: Aug 06 23:28 PDT "precice.cplscheme" time elapsed: 00:00:02 ---------------------------------------------------------- 5/27 Testing: precice.io 5/27 Test: precice.io Command: "/usr/local/bin/mpiexec" "-n" "4" "/Users/siqiwei/precice-2.1.0/build/testprecice" "--run_test=IOTests" Directory: /Users/siqiwei/precice-2.1.0/build/TestOutput/io "precice.io" start time: Aug 06 23:28 PDT Output: ---------------------------------------------------------- This test suite runs on rank 1 of 4 This test suite runs on rank 3 of 4 This test suite runs on rank 2 of 4 This test suite runs on rank 0 of 4 Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level -------------------------------------------------------------------------- Primary job terminated normally, but 1 process returned a non-zero exit code. Per user-direction, the job has been aborted. -------------------------------------------------------------------------- -------------------------------------------------------------------------- mpiexec detected that one or more processes exited with non-zero status, thus causing the job to be terminated. The first process to do so was: Process name: [[58044,1],0] Exit code: 200 -------------------------------------------------------------------------- Test time = 2.30 sec ---------------------------------------------------------- Test Failed. "precice.io" end time: Aug 06 23:28 PDT "precice.io" time elapsed: 00:00:02 ---------------------------------------------------------- 6/27 Testing: precice.m2n 6/27 Test: precice.m2n Command: "/usr/local/bin/mpiexec" "-n" "4" "/Users/siqiwei/precice-2.1.0/build/testprecice" "--run_test=M2NTests:!M2NTests/MPIPorts:!M2NTets/MPISinglePorts" Directory: /Users/siqiwei/precice-2.1.0/build/TestOutput/m2n "precice.m2n" start time: Aug 06 23:28 PDT Output: ---------------------------------------------------------- This test suite runs on rank 2 of 4 This test suite runs on rank 3 of 4 This test suite runs on rank 0 of 4 This test suite runs on rank 1 of 4 Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level -------------------------------------------------------------------------- Primary job terminated normally, but 1 process returned a non-zero exit code. Per user-direction, the job has been aborted. -------------------------------------------------------------------------- -------------------------------------------------------------------------- mpiexec detected that one or more processes exited with non-zero status, thus causing the job to be terminated. The first process to do so was: Process name: [[58033,1],0] Exit code: 200 -------------------------------------------------------------------------- Test time = 2.26 sec ---------------------------------------------------------- Test Failed. "precice.m2n" end time: Aug 06 23:28 PDT "precice.m2n" time elapsed: 00:00:02 ---------------------------------------------------------- 7/27 Testing: precice.mapping 7/27 Test: precice.mapping Command: "/usr/local/bin/mpiexec" "-n" "4" "/Users/siqiwei/precice-2.1.0/build/testprecice" "--run_test=MappingTests:!MappingTests/PetRadialBasisFunctionMapping" Directory: /Users/siqiwei/precice-2.1.0/build/TestOutput/mapping "precice.mapping" start time: Aug 06 23:28 PDT Output: ---------------------------------------------------------- This test suite runs on rank 0 of 4 This test suite runs on rank 2 of 4 This test suite runs on rank 3 of 4 This test suite runs on rank 1 of 4 Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level -------------------------------------------------------------------------- Primary job terminated normally, but 1 process returned a non-zero exit code. Per user-direction, the job has been aborted. -------------------------------------------------------------------------- -------------------------------------------------------------------------- mpiexec detected that one or more processes exited with non-zero status, thus causing the job to be terminated. The first process to do so was: Process name: [[58038,1],0] Exit code: 200 -------------------------------------------------------------------------- Test time = 2.25 sec ---------------------------------------------------------- Test Failed. "precice.mapping" end time: Aug 06 23:28 PDT "precice.mapping" time elapsed: 00:00:02 ---------------------------------------------------------- 8/27 Testing: precice.mapping.petrbf 8/27 Test: precice.mapping.petrbf Command: "/usr/local/bin/mpiexec" "-n" "4" "/Users/siqiwei/precice-2.1.0/build/testprecice" "--run_test=MappingTests/PetRadialBasisFunctionMapping" Directory: /Users/siqiwei/precice-2.1.0/build/TestOutput/mapping.petrbf "precice.mapping.petrbf" start time: Aug 06 23:28 PDT Output: ---------------------------------------------------------- This test suite runs on rank 1 of 4 This test suite runs on rank 2 of 4 This test suite runs on rank 3 of 4 This test suite runs on rank 0 of 4 Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level -------------------------------------------------------------------------- Primary job terminated normally, but 1 process returned a non-zero exit code. Per user-direction, the job has been aborted. -------------------------------------------------------------------------- -------------------------------------------------------------------------- mpiexec detected that one or more processes exited with non-zero status, thus causing the job to be terminated. The first process to do so was: Process name: [[57995,1],0] Exit code: 200 -------------------------------------------------------------------------- Test time = 2.26 sec ---------------------------------------------------------- Test Failed. "precice.mapping.petrbf" end time: Aug 06 23:28 PDT "precice.mapping.petrbf" time elapsed: 00:00:02 ---------------------------------------------------------- 9/27 Testing: precice.math 9/27 Test: precice.math Command: "/usr/local/bin/mpiexec" "-n" "4" "/Users/siqiwei/precice-2.1.0/build/testprecice" "--run_test=MathTests" Directory: /Users/siqiwei/precice-2.1.0/build/TestOutput/math "precice.math" start time: Aug 06 23:28 PDT Output: ---------------------------------------------------------- This test suite runs on rank 2 of 4 This test suite runs on rank 3 of 4 This test suite runs on rank 0 of 4 This test suite runs on rank 1 of 4 Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level -------------------------------------------------------------------------- Primary job terminated normally, but 1 process returned a non-zero exit code. Per user-direction, the job has been aborted. -------------------------------------------------------------------------- -------------------------------------------------------------------------- mpiexec detected that one or more processes exited with non-zero status, thus causing the job to be terminated. The first process to do so was: Process name: [[57984,1],0] Exit code: 200 -------------------------------------------------------------------------- Test time = 2.26 sec ---------------------------------------------------------- Test Failed. "precice.math" end time: Aug 06 23:28 PDT "precice.math" time elapsed: 00:00:02 ---------------------------------------------------------- 10/27 Testing: precice.mesh 10/27 Test: precice.mesh Command: "/usr/local/bin/mpiexec" "-n" "4" "/Users/siqiwei/precice-2.1.0/build/testprecice" "--run_test=MeshTests" Directory: /Users/siqiwei/precice-2.1.0/build/TestOutput/mesh "precice.mesh" start time: Aug 06 23:28 PDT Output: ---------------------------------------------------------- This test suite runs on rank 0 of 4 This test suite runs on rank 2 of 4 This test suite runs on rank 3 of 4 This test suite runs on rank 1 of 4 Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level -------------------------------------------------------------------------- Primary job terminated normally, but 1 process returned a non-zero exit code. Per user-direction, the job has been aborted. -------------------------------------------------------------------------- -------------------------------------------------------------------------- mpiexec detected that one or more processes exited with non-zero status, thus causing the job to be terminated. The first process to do so was: Process name: [[57989,1],0] Exit code: 200 -------------------------------------------------------------------------- Test time = 2.26 sec ---------------------------------------------------------- Test Failed. "precice.mesh" end time: Aug 06 23:28 PDT "precice.mesh" time elapsed: 00:00:02 ---------------------------------------------------------- 11/27 Testing: precice.partition 11/27 Test: precice.partition Command: "/usr/local/bin/mpiexec" "-n" "4" "/Users/siqiwei/precice-2.1.0/build/testprecice" "--run_test=PartitionTests" Directory: /Users/siqiwei/precice-2.1.0/build/TestOutput/partition "precice.partition" start time: Aug 06 23:28 PDT Output: ---------------------------------------------------------- This test suite runs on rank 3 of 4 This test suite runs on rank 0 of 4 This test suite runs on rank 1 of 4 This test suite runs on rank 2 of 4 Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level -------------------------------------------------------------------------- Primary job terminated normally, but 1 process returned a non-zero exit code. Per user-direction, the job has been aborted. -------------------------------------------------------------------------- -------------------------------------------------------------------------- mpiexec detected that one or more processes exited with non-zero status, thus causing the job to be terminated. The first process to do so was: Process name: [[58011,1],0] Exit code: 200 -------------------------------------------------------------------------- Test time = 2.26 sec ---------------------------------------------------------- Test Failed. "precice.partition" end time: Aug 06 23:28 PDT "precice.partition" time elapsed: 00:00:02 ---------------------------------------------------------- 12/27 Testing: precice.interface 12/27 Test: precice.interface Command: "/usr/local/bin/mpiexec" "-n" "4" "/Users/siqiwei/precice-2.1.0/build/testprecice" "--run_test=PreciceTests:!PreciceTests/Serial:!PreciceTests/Parallel" Directory: /Users/siqiwei/precice-2.1.0/build/TestOutput/interface "precice.interface" start time: Aug 06 23:28 PDT Output: ---------------------------------------------------------- This test suite runs on rank 2 of 4 This test suite runs on rank 3 of 4 This test suite runs on rank 0 of 4 This test suite runs on rank 1 of 4 Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level -------------------------------------------------------------------------- Primary job terminated normally, but 1 process returned a non-zero exit code. Per user-direction, the job has been aborted. -------------------------------------------------------------------------- -------------------------------------------------------------------------- mpiexec detected that one or more processes exited with non-zero status, thus causing the job to be terminated. The first process to do so was: Process name: [[58000,1],0] Exit code: 200 -------------------------------------------------------------------------- Test time = 2.26 sec ---------------------------------------------------------- Test Failed. "precice.interface" end time: Aug 06 23:28 PDT "precice.interface" time elapsed: 00:00:02 ---------------------------------------------------------- 13/27 Testing: precice.serial 13/27 Test: precice.serial Command: "/usr/local/bin/mpiexec" "-n" "4" "/Users/siqiwei/precice-2.1.0/build/testprecice" "--run_test=PreciceTests/Serial" Directory: /Users/siqiwei/precice-2.1.0/build/TestOutput/serial "precice.serial" start time: Aug 06 23:28 PDT Output: ---------------------------------------------------------- This test suite runs on rank 1 of 4 This test suite runs on rank 3 of 4 This test suite runs on rank 0 of 4 This test suite runs on rank 2 of 4 Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level -------------------------------------------------------------------------- Primary job terminated normally, but 1 process returned a non-zero exit code. Per user-direction, the job has been aborted. -------------------------------------------------------------------------- -------------------------------------------------------------------------- mpiexec detected that one or more processes exited with non-zero status, thus causing the job to be terminated. The first process to do so was: Process name: [[58005,1],0] Exit code: 200 -------------------------------------------------------------------------- Test time = 2.25 sec ---------------------------------------------------------- Test Failed. "precice.serial" end time: Aug 06 23:28 PDT "precice.serial" time elapsed: 00:00:02 ---------------------------------------------------------- 14/27 Testing: precice.parallel 14/27 Test: precice.parallel Command: "/usr/local/bin/mpiexec" "-n" "4" "/Users/siqiwei/precice-2.1.0/build/testprecice" "--run_test=PreciceTests/Parallel" Directory: /Users/siqiwei/precice-2.1.0/build/TestOutput/parallel "precice.parallel" start time: Aug 06 23:28 PDT Output: ---------------------------------------------------------- This test suite runs on rank 0 of 4 This test suite runs on rank 2 of 4 This test suite runs on rank 3 of 4 This test suite runs on rank 1 of 4 Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level -------------------------------------------------------------------------- Primary job terminated normally, but 1 process returned a non-zero exit code. Per user-direction, the job has been aborted. -------------------------------------------------------------------------- -------------------------------------------------------------------------- mpiexec detected that one or more processes exited with non-zero status, thus causing the job to be terminated. The first process to do so was: Process name: [[57962,1],0] Exit code: 200 -------------------------------------------------------------------------- Test time = 2.27 sec ---------------------------------------------------------- Test Failed. "precice.parallel" end time: Aug 06 23:28 PDT "precice.parallel" time elapsed: 00:00:02 ---------------------------------------------------------- 15/27 Testing: precice.query 15/27 Test: precice.query Command: "/usr/local/bin/mpiexec" "-n" "4" "/Users/siqiwei/precice-2.1.0/build/testprecice" "--run_test=QueryTests" Directory: /Users/siqiwei/precice-2.1.0/build/TestOutput/query "precice.query" start time: Aug 06 23:28 PDT Output: ---------------------------------------------------------- This test suite runs on rank 0 of 4 This test suite runs on rank 1 of 4 This test suite runs on rank 2 of 4 This test suite runs on rank 3 of 4 Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level -------------------------------------------------------------------------- Primary job terminated normally, but 1 process returned a non-zero exit code. Per user-direction, the job has been aborted. -------------------------------------------------------------------------- -------------------------------------------------------------------------- mpiexec detected that one or more processes exited with non-zero status, thus causing the job to be terminated. The first process to do so was: Process name: [[57967,1],0] Exit code: 200 -------------------------------------------------------------------------- Test time = 2.26 sec ---------------------------------------------------------- Test Failed. "precice.query" end time: Aug 06 23:28 PDT "precice.query" time elapsed: 00:00:02 ---------------------------------------------------------- 16/27 Testing: precice.testing 16/27 Test: precice.testing Command: "/usr/local/bin/mpiexec" "-n" "4" "/Users/siqiwei/precice-2.1.0/build/testprecice" "--run_test=TestingTests" Directory: /Users/siqiwei/precice-2.1.0/build/TestOutput/testing "precice.testing" start time: Aug 06 23:28 PDT Output: ---------------------------------------------------------- This test suite runs on rank 1 of 4 This test suite runs on rank 2 of 4 This test suite runs on rank 3 of 4 This test suite runs on rank 0 of 4 Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level -------------------------------------------------------------------------- Primary job terminated normally, but 1 process returned a non-zero exit code. Per user-direction, the job has been aborted. -------------------------------------------------------------------------- -------------------------------------------------------------------------- mpiexec detected that one or more processes exited with non-zero status, thus causing the job to be terminated. The first process to do so was: Process name: [[57956,1],0] Exit code: 200 -------------------------------------------------------------------------- Test time = 2.27 sec ---------------------------------------------------------- Test Failed. "precice.testing" end time: Aug 06 23:28 PDT "precice.testing" time elapsed: 00:00:02 ---------------------------------------------------------- 17/27 Testing: precice.utils 17/27 Test: precice.utils Command: "/usr/local/bin/mpiexec" "-n" "4" "/Users/siqiwei/precice-2.1.0/build/testprecice" "--run_test=UtilsTests" Directory: /Users/siqiwei/precice-2.1.0/build/TestOutput/utils "precice.utils" start time: Aug 06 23:28 PDT Output: ---------------------------------------------------------- This test suite runs on rank 0 of 4 This test suite runs on rank 2 of 4 This test suite runs on rank 3 of 4 This test suite runs on rank 1 of 4 Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level -------------------------------------------------------------------------- Primary job terminated normally, but 1 process returned a non-zero exit code. Per user-direction, the job has been aborted. -------------------------------------------------------------------------- -------------------------------------------------------------------------- mpiexec detected that one or more processes exited with non-zero status, thus causing the job to be terminated. The first process to do so was: Process name: [[57977,1],0] Exit code: 200 -------------------------------------------------------------------------- Test time = 2.30 sec ---------------------------------------------------------- Test Failed. "precice.utils" end time: Aug 06 23:28 PDT "precice.utils" time elapsed: 00:00:02 ---------------------------------------------------------- 18/27 Testing: precice.xml 18/27 Test: precice.xml Command: "/usr/local/bin/mpiexec" "-n" "4" "/Users/siqiwei/precice-2.1.0/build/testprecice" "--run_test=XML" Directory: /Users/siqiwei/precice-2.1.0/build/TestOutput/xml "precice.xml" start time: Aug 06 23:28 PDT Output: ---------------------------------------------------------- This test suite runs on rank 0 of 4 This test suite runs on rank 1 of 4 This test suite runs on rank 2 of 4 This test suite runs on rank 3 of 4 Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level -------------------------------------------------------------------------- Primary job terminated normally, but 1 process returned a non-zero exit code. Per user-direction, the job has been aborted. -------------------------------------------------------------------------- -------------------------------------------------------------------------- mpiexec detected that one or more processes exited with non-zero status, thus causing the job to be terminated. The first process to do so was: Process name: [[57982,1],0] Exit code: 200 -------------------------------------------------------------------------- Test time = 2.27 sec ---------------------------------------------------------- Test Failed. "precice.xml" end time: Aug 06 23:29 PDT "precice.xml" time elapsed: 00:00:02 ---------------------------------------------------------- 19/27 Testing: precice.solverdummy.build.cpp 19/27 Test: precice.solverdummy.build.cpp Command: "/usr/local/Cellar/cmake/3.18.1/bin/ctest" "--build-and-test" "/Users/siqiwei/precice-2.1.0/examples/solverdummies/cpp" "/Users/siqiwei/precice-2.1.0/build/Solverdummies/cpp" "--build-generator" "Unix Makefiles" "--build-options" "-Dprecice_DIR=/Users/siqiwei/precice-2.1.0/build" "-DCMAKE_BUILD_TYPE=Debug" "-DCMAKE_CXX_COMPILER=/Library/Developer/CommandLineTools/usr/bin/c++" "-DCMAKE_C_COMPILER=/Library/Developer/CommandLineTools/usr/bin/cc" "-DCMAKE_Fortran_COMPILER=/usr/local/bin/gfortran" Directory: /Users/siqiwei/precice-2.1.0/build/Solverdummies/cpp "precice.solverdummy.build.cpp" start time: Aug 06 23:29 PDT Output: ---------------------------------------------------------- Internal cmake changing into directory: /Users/siqiwei/precice-2.1.0/build/Solverdummies/cpp ======== CMake output ====== Configuring done Generating done Build files have been written to: /Users/siqiwei/precice-2.1.0/build/Solverdummies/cpp ======== End CMake output ====== Change Dir: /Users/siqiwei/precice-2.1.0/build/Solverdummies/cpp Run Clean Command:/usr/local/bin/gmake clean gmake[1]: Entering directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/cpp' gmake[2]: Entering directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/cpp' gmake[3]: Entering directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/cpp' gmake[3]: Leaving directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/cpp' gmake[2]: Leaving directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/cpp' gmake[1]: Leaving directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/cpp' Run Build Command(s):/usr/local/bin/gmake && gmake[1]: Entering directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/cpp' gmake[2]: Entering directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/cpp' gmake[3]: Entering directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/cpp' gmake[3]: Leaving directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/cpp' gmake[3]: Entering directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/cpp' [ 50%] Building CXX object CMakeFiles/solverdummy.dir/solverdummy.cpp.o [100%] Linking CXX executable solverdummy gmake[3]: Leaving directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/cpp' [100%] Built target solverdummy gmake[2]: Leaving directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/cpp' gmake[1]: Leaving directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/cpp' Test time = 0.86 sec ---------------------------------------------------------- Test Passed. "precice.solverdummy.build.cpp" end time: Aug 06 23:29 PDT "precice.solverdummy.build.cpp" time elapsed: 00:00:00 ---------------------------------------------------------- 20/27 Testing: precice.solverdummy.build.c 20/27 Test: precice.solverdummy.build.c Command: "/usr/local/Cellar/cmake/3.18.1/bin/ctest" "--build-and-test" "/Users/siqiwei/precice-2.1.0/examples/solverdummies/c" "/Users/siqiwei/precice-2.1.0/build/Solverdummies/c" "--build-generator" "Unix Makefiles" "--build-options" "-Dprecice_DIR=/Users/siqiwei/precice-2.1.0/build" "-DCMAKE_BUILD_TYPE=Debug" "-DCMAKE_CXX_COMPILER=/Library/Developer/CommandLineTools/usr/bin/c++" "-DCMAKE_C_COMPILER=/Library/Developer/CommandLineTools/usr/bin/cc" "-DCMAKE_Fortran_COMPILER=/usr/local/bin/gfortran" Directory: /Users/siqiwei/precice-2.1.0/build/Solverdummies/c "precice.solverdummy.build.c" start time: Aug 06 23:29 PDT Output: ---------------------------------------------------------- Internal cmake changing into directory: /Users/siqiwei/precice-2.1.0/build/Solverdummies/c ======== CMake output ====== Configuring done Generating done Build files have been written to: /Users/siqiwei/precice-2.1.0/build/Solverdummies/c ======== End CMake output ====== Change Dir: /Users/siqiwei/precice-2.1.0/build/Solverdummies/c Run Clean Command:/usr/local/bin/gmake clean gmake[1]: Entering directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/c' gmake[2]: Entering directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/c' gmake[3]: Entering directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/c' gmake[3]: Leaving directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/c' gmake[2]: Leaving directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/c' gmake[1]: Leaving directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/c' Run Build Command(s):/usr/local/bin/gmake && gmake[1]: Entering directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/c' gmake[2]: Entering directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/c' gmake[3]: Entering directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/c' gmake[3]: Leaving directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/c' gmake[3]: Entering directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/c' [ 50%] Building C object CMakeFiles/solverdummy.dir/solverdummy.c.o /Users/siqiwei/precice-2.1.0/examples/solverdummies/c/solverdummy.c:82:9: warning: address of function 'precicec_isReadDataAvailable' will always evaluate to 'true' [-Wpointer-bool-conversion] if (precicec_isReadDataAvailable) { ~~ ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ /Users/siqiwei/precice-2.1.0/examples/solverdummies/c/solverdummy.c:82:9: note: prefix with the address-of operator to silence this warning if (precicec_isReadDataAvailable) { ^ & 1 warning generated. [100%] Linking C executable solverdummy gmake[3]: Leaving directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/c' [100%] Built target solverdummy gmake[2]: Leaving directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/c' gmake[1]: Leaving directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/c' Test time = 0.26 sec ---------------------------------------------------------- Test Passed. "precice.solverdummy.build.c" end time: Aug 06 23:29 PDT "precice.solverdummy.build.c" time elapsed: 00:00:00 ---------------------------------------------------------- 21/27 Testing: precice.solverdummy.build.fortran 21/27 Test: precice.solverdummy.build.fortran Command: "/usr/local/Cellar/cmake/3.18.1/bin/ctest" "--build-and-test" "/Users/siqiwei/precice-2.1.0/examples/solverdummies/fortran" "/Users/siqiwei/precice-2.1.0/build/Solverdummies/fortran" "--build-generator" "Unix Makefiles" "--build-options" "-Dprecice_DIR=/Users/siqiwei/precice-2.1.0/build" "-DCMAKE_BUILD_TYPE=Debug" "-DCMAKE_CXX_COMPILER=/Library/Developer/CommandLineTools/usr/bin/c++" "-DCMAKE_C_COMPILER=/Library/Developer/CommandLineTools/usr/bin/cc" "-DCMAKE_Fortran_COMPILER=/usr/local/bin/gfortran" Directory: /Users/siqiwei/precice-2.1.0/build/Solverdummies/fortran "precice.solverdummy.build.fortran" start time: Aug 06 23:29 PDT Output: ---------------------------------------------------------- Internal cmake changing into directory: /Users/siqiwei/precice-2.1.0/build/Solverdummies/fortran ======== CMake output ====== Configuring done Generating done Build files have been written to: /Users/siqiwei/precice-2.1.0/build/Solverdummies/fortran ======== End CMake output ====== Change Dir: /Users/siqiwei/precice-2.1.0/build/Solverdummies/fortran Run Clean Command:/usr/local/bin/gmake clean gmake[1]: Entering directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/fortran' gmake[2]: Entering directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/fortran' gmake[3]: Entering directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/fortran' gmake[3]: Leaving directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/fortran' gmake[2]: Leaving directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/fortran' gmake[1]: Leaving directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/fortran' Run Build Command(s):/usr/local/bin/gmake && gmake[1]: Entering directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/fortran' gmake[2]: Entering directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/fortran' gmake[3]: Entering directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/fortran' gmake[3]: Leaving directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/fortran' gmake[3]: Entering directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/fortran' [ 50%] Building Fortran object CMakeFiles/solverdummy.dir/solverdummy.f90.o [100%] Linking Fortran executable solverdummy gmake[3]: Leaving directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/fortran' [100%] Built target solverdummy gmake[2]: Leaving directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/fortran' gmake[1]: Leaving directory '/Users/siqiwei/precice-2.1.0/build/Solverdummies/fortran' Test time = 0.43 sec ---------------------------------------------------------- Test Passed. "precice.solverdummy.build.fortran" end time: Aug 06 23:29 PDT "precice.solverdummy.build.fortran" time elapsed: 00:00:00 ---------------------------------------------------------- 22/27 Testing: precice.solverdummy.run.cpp-cpp 22/27 Test: precice.solverdummy.run.cpp-cpp Command: "/usr/local/Cellar/cmake/3.18.1/bin/cmake" "-D" "WRAPPER=/Users/siqiwei/precice-2.1.0/cmake/runsolverdummies.sh" "-D" "DUMMY_A=/Users/siqiwei/precice-2.1.0/build/Solverdummies/cpp/solverdummy" "-D" "DUMMY_B=/Users/siqiwei/precice-2.1.0/build/Solverdummies/cpp/solverdummy" "-D" "DUMMY_RUN_DIR=/Users/siqiwei/precice-2.1.0/build/TestOutput/solverdummy.run.cpp-cpp" "-D" "DUMMY_CONFIG=/Users/siqiwei/precice-2.1.0/examples/solverdummies/precice-config.xml" "-P" "/Users/siqiwei/precice-2.1.0/cmake/runsolverdummies.cmake" Directory: /Users/siqiwei/precice-2.1.0/build/TestOutput/solverdummy.run.cpp-cpp "precice.solverdummy.run.cpp-cpp" start time: Aug 06 23:29 PDT Output: ---------------------------------------------------------- DUMMY: Running solver dummy with preCICE config file "/Users/siqiwei/precice-2.1.0/examples/solverdummies/precice-config.xml", participant name "SolverTwo", and mesh name "MeshTwo". preCICE: This is preCICE version 2.1.0 DUMMY: Running solver dummy with preCICE config file "/Users/siqiwei/precice-2.1.0/examples/solverdummies/precice-config.xml", participant name "SolverOne", and mesh name "MeshOne". preCICE: This is preCICE version 2.1.0 preCICE: Revision info: no-info [Git failed/Not a repository] preCICE: Revision info: no-info [Git failed/Not a repository] preCICE: Configuring preCICE with configuration "/Users/siqiwei/precice-2.1.0/examples/solverdummies/precice-config.xml" preCICE: Configuring preCICE with configuration "/Users/siqiwei/precice-2.1.0/examples/solverdummies/precice-config.xml" preCICE: I am participant "SolverOne" preCICE: I am participant "SolverTwo" preCICE: Setting up master communication to coupling partner/s preCICE: Setting up master communication to coupling partner/s preCICE: Masters are connected preCICE: Setting up preliminary slaves communication to coupling partner/s preCICE: Prepare partition for mesh MeshOne preCICE: Masters are connected preCICE: Setting up preliminary slaves communication to coupling partner/s preCICE: Receive global mesh MeshOne preCICE: Gather mesh MeshOne preCICE: Send global mesh MeshOne preCICE: Prepare partition for mesh MeshTwo preCICE: Setting up slaves communication to coupling partner/s preCICE: Setting up slaves communication to coupling partner/s libc++abi.dylib: terminating with uncaught exception of type boost::wrapexcept: shutdown: Socket is not connected [Vicky-Weis-Macbook-Pro-2020:95979] *** Process received signal *** [Vicky-Weis-Macbook-Pro-2020:95979] Signal: Abort trap: 6 (6) [Vicky-Weis-Macbook-Pro-2020:95979] Signal code: (0) [Vicky-Weis-Macbook-Pro-2020:95979] [ 0] 0 libsystem_platform.dylib 0x00007fff6a3065fd _sigtramp + 29 [Vicky-Weis-Macbook-Pro-2020:95979] [ 1] 0 ??? 0x0000000000000400 0x0 + 1024 [Vicky-Weis-Macbook-Pro-2020:95979] [ 2] 0 libsystem_c.dylib 0x00007fff6a1dc808 abort + 120 [Vicky-Weis-Macbook-Pro-2020:95979] [ 3] 0 libc++abi.dylib 0x00007fff6743c458 abort_message + 231 [Vicky-Weis-Macbook-Pro-2020:95979] [ 4] 0 libc++abi.dylib 0x00007fff6742d8a7 _ZL28demangling_terminate_handlerv + 238 [Vicky-Weis-Macbook-Pro-2020:95979] [ 5] 0 libobjc.A.dylib 0x00007fff68f685b1 _ZL15_objc_terminatev + 104 [Vicky-Weis-Macbook-Pro-2020:95979] [ 6] 0 libc++abi.dylib 0x00007fff6743b887 _ZSt11__terminatePFvvE + 8 [Vicky-Weis-Macbook-Pro-2020:95979] [ 7] 0 libc++abi.dylib 0x00007fff6743b829 _ZSt9terminatev + 41 [Vicky-Weis-Macbook-Pro-2020:95979] [ 8] 0 libprecice.2.1.0.dylib 0x0000000109d235b5 _ZN7precice3com19SocketCommunicationD1Ev + 21 [Vicky-Weis-Macbook-Pro-2020:95979] [ 9] 0 libprecice.2.1.0.dylib 0x0000000109d7c136 _ZNSt3__120__shared_ptr_emplaceIN7precice3com19SocketCommunicationENS_9allocatorIS3_EEE16__on_zero_sharedEv + 38 [Vicky-Weis-Macbook-Pro-2020:95979] [10] 0 libprecice.2.1.0.dylib 0x0000000109b3d50d _ZNSt3__114__shared_count16__release_sharedEv + 61 [Vicky-Weis-Macbook-Pro-2020:95979] [11] 0 libprecice.2.1.0.dylib 0x0000000109b3d4af _ZNSt3__119__shared_weak_count16__release_sharedEv + 31 [Vicky-Weis-Macbook-Pro-2020:95979] [12] 0 libprecice.2.1.0.dylib 0x0000000109b3d47c _ZNSt3__110shared_ptrIN7precice12acceleration4impl14PreconditionerEED2Ev + 44 [Vicky-Weis-Macbook-Pro-2020:95979] [13] 0 libprecice.2.1.0.dylib 0x0000000109b3d445 _ZNSt3__110shared_ptrIN7precice12acceleration4impl14PreconditionerEED1Ev + 21 [Vicky-Weis-Macbook-Pro-2020:95979] [14] 0 libprecice.2.1.0.dylib 0x0000000109eba32c _ZN7precice3m2n25PointToPointCommunication16acceptConnectionERKNSt3__112basic_stringIcNS2_11char_traitsIcEENS2_9allocatorIcEEEESA_ + 1884 [Vicky-Weis-Macbook-Pro-2020:95979] [15] 0 libprecice.2.1.0.dylib 0x0000000109eaa9e5 _ZN7precice3m2n3M2N22acceptSlavesConnectionERKNSt3__112basic_stringIcNS2_11char_traitsIcEENS2_9allocatorIcEEEESA_ + 1365 [Vicky-Weis-Macbook-Pro-2020:95979] [16] 0 libprecice.2.1.0.dylib 0x0000000109e9b960 _ZN7precice3m2n8BoundM2N13connectSlavesEv + 752 [Vicky-Weis-Macbook-Pro-2020:95979] [17] 0 libprecice.2.1.0.dylib 0x000000010a20964a _ZN7precice4impl19SolverInterfaceImpl10initializeEv + 3226 [Vicky-Weis-Macbook-Pro-2020:95979] [18] 0 libprecice.2.1.0.dylib 0x000000010a1b55cd _ZN7precice15SolverInterface10initializeEv + 29 [Vicky-Weis-Macbook-Pro-2020:95979] [19] 0 solverdummy 0x0000000108e96a6e main + 1422 [Vicky-Weis-Macbook-Pro-2020:95979] [20] 0 libdyld.dylib 0x00007fff6a10dcc9 start + 1 [Vicky-Weis-Macbook-Pro-2020:95979] *** End of error message *** /Users/siqiwei/precice-2.1.0/cmake/runsolverdummies.sh: line 9: 95979 Abort trap: 6 $2 $3 SolverTwo MeshTwo Test time = 60.10 sec ---------------------------------------------------------- Test Failed. "precice.solverdummy.run.cpp-cpp" end time: Aug 06 23:30 PDT "precice.solverdummy.run.cpp-cpp" time elapsed: 00:01:00 ---------------------------------------------------------- 23/27 Testing: precice.solverdummy.run.c-c 23/27 Test: precice.solverdummy.run.c-c Command: "/usr/local/Cellar/cmake/3.18.1/bin/cmake" "-D" "WRAPPER=/Users/siqiwei/precice-2.1.0/cmake/runsolverdummies.sh" "-D" "DUMMY_A=/Users/siqiwei/precice-2.1.0/build/Solverdummies/c/solverdummy" "-D" "DUMMY_B=/Users/siqiwei/precice-2.1.0/build/Solverdummies/c/solverdummy" "-D" "DUMMY_RUN_DIR=/Users/siqiwei/precice-2.1.0/build/TestOutput/solverdummy.run.c-c" "-D" "DUMMY_CONFIG=/Users/siqiwei/precice-2.1.0/examples/solverdummies/precice-config.xml" "-P" "/Users/siqiwei/precice-2.1.0/cmake/runsolverdummies.cmake" Directory: /Users/siqiwei/precice-2.1.0/build/TestOutput/solverdummy.run.c-c "precice.solverdummy.run.c-c" start time: Aug 06 23:30 PDT Output: ---------------------------------------------------------- DUMMY: Running solver dummy with preCICE config file "/Users/siqiwei/precice-2.1.0/examples/solverdummies/precice-config.xml", participant name "SolverOne", and mesh name "MeshOne". preCICE: This is preCICE version 2.1.0 DUMMY: Running solver dummy with preCICE config file "/Users/siqiwei/precice-2.1.0/examples/solverdummies/precice-config.xml", participant name "SolverTwo", and mesh name "MeshTwo". preCICE: This is preCICE version 2.1.0 preCICE: Revision info: no-info [Git failed/Not a repository] preCICE: Configuring preCICE with configuration "/Users/siqiwei/precice-2.1.0/examples/solverdummies/precice-config.xml" preCICE: Revision info: no-info [Git failed/Not a repository] preCICE: I am participant "SolverOne" preCICE: Configuring preCICE with configuration "/Users/siqiwei/precice-2.1.0/examples/solverdummies/precice-config.xml" preCICE: I am participant "SolverTwo" preCICE: Setting up master communication to coupling partner/s preCICE: Setting up master communication to coupling partner/s preCICE: Masters are connected preCICE: Setting up preliminary slaves communication to coupling partner/s preCICE: Prepare partition for mesh MeshOne preCICE: Masters are connected preCICE: Setting up preliminary slaves communication to coupling partner/s preCICE: Receive global mesh MeshOne preCICE: Gather mesh MeshOne preCICE: Send global mesh MeshOne preCICE: Setting up slaves communication to coupling partner/s preCICE: Prepare partition for mesh MeshTwo preCICE: Setting up slaves communication to coupling partner/s libc++abi.dylib: terminating with uncaught exception of type boost::wrapexcept: shutdown: Socket is not connected [Vicky-Weis-Macbook-Pro-2020:95999] *** Process received signal *** [Vicky-Weis-Macbook-Pro-2020:95999] Signal: Abort trap: 6 (6) [Vicky-Weis-Macbook-Pro-2020:95999] Signal code: (0) [Vicky-Weis-Macbook-Pro-2020:95999] [ 0] 0 libsystem_platform.dylib 0x00007fff6a3065fd _sigtramp + 29 [Vicky-Weis-Macbook-Pro-2020:95999] [ 1] 0 ??? 0x0000000000000400 0x0 + 1024 [Vicky-Weis-Macbook-Pro-2020:95999] [ 2] 0 libsystem_c.dylib 0x00007fff6a1dc808 abort + 120 [Vicky-Weis-Macbook-Pro-2020:95999] [ 3] 0 libc++abi.dylib 0x00007fff6743c458 abort_message + 231 [Vicky-Weis-Macbook-Pro-2020:95999] [ 4] 0 libc++abi.dylib 0x00007fff6742d8a7 _ZL28demangling_terminate_handlerv + 238 [Vicky-Weis-Macbook-Pro-2020:95999] [ 5] 0 libobjc.A.dylib 0x00007fff68f685b1 _ZL15_objc_terminatev + 104 [Vicky-Weis-Macbook-Pro-2020:95999] [ 6] 0 libc++abi.dylib 0x00007fff6743b887 _ZSt11__terminatePFvvE + 8 [Vicky-Weis-Macbook-Pro-2020:95999] [ 7] 0 libc++abi.dylib 0x00007fff6743b829 _ZSt9terminatev + 41 [Vicky-Weis-Macbook-Pro-2020:95999] [ 8] 0 libprecice.2.1.0.dylib 0x00000001005885b5 _ZN7precice3com19SocketCommunicationD1Ev + 21 [Vicky-Weis-Macbook-Pro-2020:95999] [ 9] 0 libprecice.2.1.0.dylib 0x00000001005e1136 _ZNSt3__120__shared_ptr_emplaceIN7precice3com19SocketCommunicationENS_9allocatorIS3_EEE16__on_zero_sharedEv + 38 [Vicky-Weis-Macbook-Pro-2020:95999] [10] 0 libprecice.2.1.0.dylib 0x00000001003a250d _ZNSt3__114__shared_count16__release_sharedEv + 61 [Vicky-Weis-Macbook-Pro-2020:95999] [11] 0 libprecice.2.1.0.dylib 0x00000001003a24af _ZNSt3__119__shared_weak_count16__release_sharedEv + 31 [Vicky-Weis-Macbook-Pro-2020:95999] [12] 0 libprecice.2.1.0.dylib 0x00000001003a247c _ZNSt3__110shared_ptrIN7precice12acceleration4impl14PreconditionerEED2Ev + 44 [Vicky-Weis-Macbook-Pro-2020:95999] [13] 0 libprecice.2.1.0.dylib 0x00000001003a2445 _ZNSt3__110shared_ptrIN7precice12acceleration4impl14PreconditionerEED1Ev + 21 [Vicky-Weis-Macbook-Pro-2020:95999] [14] 0 libprecice.2.1.0.dylib 0x000000010071f32c _ZN7precice3m2n25PointToPointCommunication16acceptConnectionERKNSt3__112basic_stringIcNS2_11char_traitsIcEENS2_9allocatorIcEEEESA_ + 1884 [Vicky-Weis-Macbook-Pro-2020:95999] [15] 0 libprecice.2.1.0.dylib 0x000000010070f9e5 _ZN7precice3m2n3M2N22acceptSlavesConnectionERKNSt3__112basic_stringIcNS2_11char_traitsIcEENS2_9allocatorIcEEEESA_ + 1365 [Vicky-Weis-Macbook-Pro-2020:95999] [16] 0 libprecice.2.1.0.dylib 0x0000000100700960 _ZN7precice3m2n8BoundM2N13connectSlavesEv + 752 [Vicky-Weis-Macbook-Pro-2020:95999] [17] 0 libprecice.2.1.0.dylib 0x0000000100a6e64a _ZN7precice4impl19SolverInterfaceImpl10initializeEv + 3226 [Vicky-Weis-Macbook-Pro-2020:95999] [18] 0 libprecice.2.1.0.dylib 0x0000000100a1a5cd _ZN7precice15SolverInterface10initializeEv + 29 [Vicky-Weis-Macbook-Pro-2020:95999] [19] 0 libprecice.2.1.0.dylib 0x0000000100bac1c7 precicec_initialize + 167 [Vicky-Weis-Macbook-Pro-2020:95999] [20] 0 solverdummy 0x0000000100388a86 main + 806 [Vicky-Weis-Macbook-Pro-2020:95999] [21] 0 libdyld.dylib 0x00007fff6a10dcc9 start + 1 [Vicky-Weis-Macbook-Pro-2020:95999] *** End of error message *** /Users/siqiwei/precice-2.1.0/cmake/runsolverdummies.sh: line 9: 95999 Abort trap: 6 $2 $3 SolverTwo MeshTwo Test time = 60.10 sec ---------------------------------------------------------- Test Failed. "precice.solverdummy.run.c-c" end time: Aug 06 23:31 PDT "precice.solverdummy.run.c-c" time elapsed: 00:01:00 ---------------------------------------------------------- 24/27 Testing: precice.solverdummy.run.fortran-fortran 24/27 Test: precice.solverdummy.run.fortran-fortran Command: "/usr/local/Cellar/cmake/3.18.1/bin/cmake" "-D" "WRAPPER=/Users/siqiwei/precice-2.1.0/cmake/runsolverdummies.sh" "-D" "DUMMY_A=/Users/siqiwei/precice-2.1.0/build/Solverdummies/fortran/solverdummy" "-D" "DUMMY_B=/Users/siqiwei/precice-2.1.0/build/Solverdummies/fortran/solverdummy" "-D" "DUMMY_RUN_DIR=/Users/siqiwei/precice-2.1.0/build/TestOutput/solverdummy.run.fortran-fortran" "-D" "DUMMY_CONFIG=/Users/siqiwei/precice-2.1.0/examples/solverdummies/precice-config.xml" "-P" "/Users/siqiwei/precice-2.1.0/cmake/runsolverdummies.cmake" Directory: /Users/siqiwei/precice-2.1.0/build/TestOutput/solverdummy.run.fortran-fortran "precice.solverdummy.run.fortran-fortran" start time: Aug 06 23:31 PDT Output: ---------------------------------------------------------- DUMMY: Starting Fortran solver dummy... DUMMY: Starting Fortran solver dummy... preCICE: This is preCICE version 2.1.0 preCICE: This is preCICE version 2.1.0 preCICE: Revision info: no-info [Git failed/Not a repository] preCICE: Revision info: no-info [Git failed/Not a repository] preCICE: Configuring preCICE with configuration "/Users/siqiwei/precice-2.1.0/examples/solverdummies/precice-config.xml" preCICE: Configuring preCICE with configuration "/Users/siqiwei/precice-2.1.0/examples/solverdummies/precice-config.xml" preCICE: I am participant "SolverOne" preCICE: I am participant "SolverTwo" preCICE: Setting up master communication to coupling partner/s preCICE: Setting up master communication to coupling partner/s preCICE: Masters are connected preCICE: Setting up preliminary slaves communication to coupling partner/s preCICE: Prepare partition for mesh MeshOne preCICE: Masters are connected preCICE: Gather mesh MeshOne preCICE: Setting up preliminary slaves communication to coupling partner/s preCICE: Receive global mesh MeshOne preCICE: Send global mesh MeshOne preCICE: Setting up slaves communication to coupling partner/s preCICE: Prepare partition for mesh MeshTwo preCICE: Setting up slaves communication to coupling partner/s libc++abi.dylib: terminating with uncaught exception of type boost::wrapexcept: shutdown: Socket is not connected Program received signal SIGABRT: Process abort signal. Backtrace for this error: #0 0x10d533ebd #1 0x10d5332ed #2 0x7fff6a3065fc /Users/siqiwei/precice-2.1.0/cmake/runsolverdummies.sh: line 9: 96025 Abort trap: 6 $2 $3 SolverTwo MeshTwo Test time = 60.11 sec ---------------------------------------------------------- Test Failed. "precice.solverdummy.run.fortran-fortran" end time: Aug 06 23:32 PDT "precice.solverdummy.run.fortran-fortran" time elapsed: 00:01:00 ---------------------------------------------------------- 25/27 Testing: precice.solverdummy.run.cpp-c 25/27 Test: precice.solverdummy.run.cpp-c Command: "/usr/local/Cellar/cmake/3.18.1/bin/cmake" "-D" "WRAPPER=/Users/siqiwei/precice-2.1.0/cmake/runsolverdummies.sh" "-D" "DUMMY_A=/Users/siqiwei/precice-2.1.0/build/Solverdummies/cpp/solverdummy" "-D" "DUMMY_B=/Users/siqiwei/precice-2.1.0/build/Solverdummies/c/solverdummy" "-D" "DUMMY_RUN_DIR=/Users/siqiwei/precice-2.1.0/build/TestOutput/solverdummy.run.cpp-c" "-D" "DUMMY_CONFIG=/Users/siqiwei/precice-2.1.0/examples/solverdummies/precice-config.xml" "-P" "/Users/siqiwei/precice-2.1.0/cmake/runsolverdummies.cmake" Directory: /Users/siqiwei/precice-2.1.0/build/TestOutput/solverdummy.run.cpp-c "precice.solverdummy.run.cpp-c" start time: Aug 06 23:32 PDT Output: ---------------------------------------------------------- DUMMY: Running solver dummy with preCICE config file "/Users/siqiwei/precice-2.1.0/examples/solverdummies/precice-config.xml", participant name "SolverTwo", and mesh name "MeshTwo". preCICE: This is preCICE version 2.1.0 DUMMY: Running solver dummy with preCICE config file "/Users/siqiwei/precice-2.1.0/examples/solverdummies/precice-config.xml", participant name "SolverOne", and mesh name "MeshOne". preCICE: This is preCICE version 2.1.0 preCICE: Revision info: no-info [Git failed/Not a repository] preCICE: Revision info: no-info [Git failed/Not a repository] preCICE: Configuring preCICE with configuration "/Users/siqiwei/precice-2.1.0/examples/solverdummies/precice-config.xml" preCICE: Configuring preCICE with configuration "/Users/siqiwei/precice-2.1.0/examples/solverdummies/precice-config.xml" preCICE: I am participant "SolverTwo" preCICE: I am participant "SolverOne" preCICE: Setting up master communication to coupling partner/s preCICE: Setting up master communication to coupling partner/s preCICE: Masters are connected preCICE: Setting up preliminary slaves communication to coupling partner/s preCICE: Prepare partition for mesh MeshOne preCICE: Masters are connected preCICE: Setting up preliminary slaves communication to coupling partner/s preCICE: Receive global mesh MeshOne preCICE: Gather mesh MeshOne preCICE: Send global mesh MeshOne preCICE: Prepare partition for mesh MeshTwo preCICE: Setting up slaves communication to coupling partner/s preCICE: Setting up slaves communication to coupling partner/s libc++abi.dylib: terminating with uncaught exception of type boost::wrapexcept: shutdown: Socket is not connected [Vicky-Weis-Macbook-Pro-2020:96037] *** Process received signal *** [Vicky-Weis-Macbook-Pro-2020:96037] Signal: Abort trap: 6 (6) [Vicky-Weis-Macbook-Pro-2020:96037] Signal code: (0) [Vicky-Weis-Macbook-Pro-2020:96037] [ 0] 0 libsystem_platform.dylib 0x00007fff6a3065fd _sigtramp + 29 [Vicky-Weis-Macbook-Pro-2020:96037] [ 1] 0 ??? 0x0000000000000400 0x0 + 1024 [Vicky-Weis-Macbook-Pro-2020:96037] [ 2] 0 libsystem_c.dylib 0x00007fff6a1dc808 abort + 120 [Vicky-Weis-Macbook-Pro-2020:96037] [ 3] 0 libc++abi.dylib 0x00007fff6743c458 abort_message + 231 [Vicky-Weis-Macbook-Pro-2020:96037] [ 4] 0 libc++abi.dylib 0x00007fff6742d8a7 _ZL28demangling_terminate_handlerv + 238 [Vicky-Weis-Macbook-Pro-2020:96037] [ 5] 0 libobjc.A.dylib 0x00007fff68f685b1 _ZL15_objc_terminatev + 104 [Vicky-Weis-Macbook-Pro-2020:96037] [ 6] 0 libc++abi.dylib 0x00007fff6743b887 _ZSt11__terminatePFvvE + 8 [Vicky-Weis-Macbook-Pro-2020:96037] [ 7] 0 libc++abi.dylib 0x00007fff6743b829 _ZSt9terminatev + 41 [Vicky-Weis-Macbook-Pro-2020:96037] [ 8] 0 libprecice.2.1.0.dylib 0x0000000103eca5b5 _ZN7precice3com19SocketCommunicationD1Ev + 21 [Vicky-Weis-Macbook-Pro-2020:96037] [ 9] 0 libprecice.2.1.0.dylib 0x0000000103f23136 _ZNSt3__120__shared_ptr_emplaceIN7precice3com19SocketCommunicationENS_9allocatorIS3_EEE16__on_zero_sharedEv + 38 [Vicky-Weis-Macbook-Pro-2020:96037] [10] 0 libprecice.2.1.0.dylib 0x0000000103ce450d _ZNSt3__114__shared_count16__release_sharedEv + 61 [Vicky-Weis-Macbook-Pro-2020:96037] [11] 0 libprecice.2.1.0.dylib 0x0000000103ce44af _ZNSt3__119__shared_weak_count16__release_sharedEv + 31 [Vicky-Weis-Macbook-Pro-2020:96037] [12] 0 libprecice.2.1.0.dylib 0x0000000103ce447c _ZNSt3__110shared_ptrIN7precice12acceleration4impl14PreconditionerEED2Ev + 44 [Vicky-Weis-Macbook-Pro-2020:96037] [13] 0 libprecice.2.1.0.dylib 0x0000000103ce4445 _ZNSt3__110shared_ptrIN7precice12acceleration4impl14PreconditionerEED1Ev + 21 [Vicky-Weis-Macbook-Pro-2020:96037] [14] 0 libprecice.2.1.0.dylib 0x000000010406132c _ZN7precice3m2n25PointToPointCommunication16acceptConnectionERKNSt3__112basic_stringIcNS2_11char_traitsIcEENS2_9allocatorIcEEEESA_ + 1884 [Vicky-Weis-Macbook-Pro-2020:96037] [15] 0 libprecice.2.1.0.dylib 0x00000001040519e5 _ZN7precice3m2n3M2N22acceptSlavesConnectionERKNSt3__112basic_stringIcNS2_11char_traitsIcEENS2_9allocatorIcEEEESA_ + 1365 [Vicky-Weis-Macbook-Pro-2020:96037] [16] 0 libprecice.2.1.0.dylib 0x0000000104042960 _ZN7precice3m2n8BoundM2N13connectSlavesEv + 752 [Vicky-Weis-Macbook-Pro-2020:96037] [17] 0 libprecice.2.1.0.dylib 0x00000001043b064a _ZN7precice4impl19SolverInterfaceImpl10initializeEv + 3226 [Vicky-Weis-Macbook-Pro-2020:96037] [18] 0 libprecice.2.1.0.dylib 0x000000010435c5cd _ZN7precice15SolverInterface10initializeEv + 29 [Vicky-Weis-Macbook-Pro-2020:96037] [19] 0 libprecice.2.1.0.dylib 0x00000001044ee1c7 precicec_initialize + 167 [Vicky-Weis-Macbook-Pro-2020:96037] [20] 0 solverdummy 0x0000000103cc8a86 main + 806 [Vicky-Weis-Macbook-Pro-2020:96037] [21] 0 libdyld.dylib 0x00007fff6a10dcc9 start + 1 [Vicky-Weis-Macbook-Pro-2020:96037] *** End of error message *** /Users/siqiwei/precice-2.1.0/cmake/runsolverdummies.sh: line 9: 96037 Abort trap: 6 $2 $3 SolverTwo MeshTwo Test time = 60.10 sec ---------------------------------------------------------- Test Failed. "precice.solverdummy.run.cpp-c" end time: Aug 06 23:33 PDT "precice.solverdummy.run.cpp-c" time elapsed: 00:01:00 ---------------------------------------------------------- 26/27 Testing: precice.solverdummy.run.cpp-fortran 26/27 Test: precice.solverdummy.run.cpp-fortran Command: "/usr/local/Cellar/cmake/3.18.1/bin/cmake" "-D" "WRAPPER=/Users/siqiwei/precice-2.1.0/cmake/runsolverdummies.sh" "-D" "DUMMY_A=/Users/siqiwei/precice-2.1.0/build/Solverdummies/cpp/solverdummy" "-D" "DUMMY_B=/Users/siqiwei/precice-2.1.0/build/Solverdummies/fortran/solverdummy" "-D" "DUMMY_RUN_DIR=/Users/siqiwei/precice-2.1.0/build/TestOutput/solverdummy.run.cpp-fortran" "-D" "DUMMY_CONFIG=/Users/siqiwei/precice-2.1.0/examples/solverdummies/precice-config.xml" "-P" "/Users/siqiwei/precice-2.1.0/cmake/runsolverdummies.cmake" Directory: /Users/siqiwei/precice-2.1.0/build/TestOutput/solverdummy.run.cpp-fortran "precice.solverdummy.run.cpp-fortran" start time: Aug 06 23:33 PDT Output: ---------------------------------------------------------- DUMMY: Starting Fortran solver dummy... DUMMY: Running solver dummy with preCICE config file "/Users/siqiwei/precice-2.1.0/examples/solverdummies/precice-config.xml", participant name "SolverOne", and mesh name "MeshOne". preCICE: This is preCICE version 2.1.0 preCICE: This is preCICE version 2.1.0 preCICE: Revision info: no-info [Git failed/Not a repository] preCICE: Revision info: no-info [Git failed/Not a repository] preCICE: Configuring preCICE with configuration "/Users/siqiwei/precice-2.1.0/examples/solverdummies/precice-config.xml" preCICE: Configuring preCICE with configuration "/Users/siqiwei/precice-2.1.0/examples/solverdummies/precice-config.xml" preCICE: I am participant "SolverOne" preCICE: I am participant "SolverTwo" preCICE: Setting up master communication to coupling partner/s preCICE: Setting up master communication to coupling partner/s preCICE: Masters are connected preCICE: Setting up preliminary slaves communication to coupling partner/s preCICE: Prepare partition for mesh MeshOne preCICE: Masters are connected preCICE: Setting up preliminary slaves communication to coupling partner/s preCICE: Receive global mesh MeshOne preCICE: Gather mesh MeshOne preCICE: Send global mesh MeshOne preCICE: Setting up slaves communication to coupling partner/s preCICE: Prepare partition for mesh MeshTwo preCICE: Setting up slaves communication to coupling partner/s libc++abi.dylib: terminating with uncaught exception of type boost::wrapexcept: shutdown: Socket is not connected Program received signal SIGABRT: Process abort signal. Backtrace for this error: #0 0x10ac50ebd #1 0x10ac502ed #2 0x7fff6a3065fc /Users/siqiwei/precice-2.1.0/cmake/runsolverdummies.sh: line 9: 96064 Abort trap: 6 $2 $3 SolverTwo MeshTwo Test time = 60.14 sec ---------------------------------------------------------- Test Failed. "precice.solverdummy.run.cpp-fortran" end time: Aug 06 23:34 PDT "precice.solverdummy.run.cpp-fortran" time elapsed: 00:01:00 ---------------------------------------------------------- 27/27 Testing: precice.solverdummy.run.c-fortran 27/27 Test: precice.solverdummy.run.c-fortran Command: "/usr/local/Cellar/cmake/3.18.1/bin/cmake" "-D" "WRAPPER=/Users/siqiwei/precice-2.1.0/cmake/runsolverdummies.sh" "-D" "DUMMY_A=/Users/siqiwei/precice-2.1.0/build/Solverdummies/c/solverdummy" "-D" "DUMMY_B=/Users/siqiwei/precice-2.1.0/build/Solverdummies/fortran/solverdummy" "-D" "DUMMY_RUN_DIR=/Users/siqiwei/precice-2.1.0/build/TestOutput/solverdummy.run.c-fortran" "-D" "DUMMY_CONFIG=/Users/siqiwei/precice-2.1.0/examples/solverdummies/precice-config.xml" "-P" "/Users/siqiwei/precice-2.1.0/cmake/runsolverdummies.cmake" Directory: /Users/siqiwei/precice-2.1.0/build/TestOutput/solverdummy.run.c-fortran "precice.solverdummy.run.c-fortran" start time: Aug 06 23:34 PDT Output: ---------------------------------------------------------- DUMMY: Starting Fortran solver dummy... preCICE: This is preCICE version 2.1.0 preCICE: Revision info: no-info [Git failed/Not a repository] preCICE: Configuring preCICE with configuration "/Users/siqiwei/precice-2.1.0/examples/solverdummies/precice-config.xml" preCICE: I am participant "SolverTwo" DUMMY: Running solver dummy with preCICE config file "/Users/siqiwei/precice-2.1.0/examples/solverdummies/precice-config.xml", participant name "SolverOne", and mesh name "MeshOne". preCICE: This is preCICE version 2.1.0 preCICE: Revision info: no-info [Git failed/Not a repository] preCICE: Configuring preCICE with configuration "/Users/siqiwei/precice-2.1.0/examples/solverdummies/precice-config.xml" preCICE: I am participant "SolverOne" preCICE: Setting up master communication to coupling partner/s preCICE: Setting up master communication to coupling partner/s preCICE: Masters are connected preCICE: Setting up preliminary slaves communication to coupling partner/s preCICE: Prepare partition for mesh MeshOne preCICE: Masters are connected preCICE: Setting up preliminary slaves communication to coupling partner/s preCICE: Receive global mesh MeshOne preCICE: Gather mesh MeshOne preCICE: Send global mesh MeshOne preCICE: Setting up slaves communication to coupling partner/s preCICE: Prepare partition for mesh MeshTwo preCICE: Setting up slaves communication to coupling partner/s libc++abi.dylib: terminating with uncaught exception of type boost::wrapexcept: shutdown: Socket is not connected Program received signal SIGABRT: Process abort signal. Backtrace for this error: #0 0x10d2ecebd #1 0x10d2ec2ed #2 0x7fff6a3065fc /Users/siqiwei/precice-2.1.0/cmake/runsolverdummies.sh: line 9: 96136 Abort trap: 6 $2 $3 SolverTwo MeshTwo Test time = 60.09 sec ---------------------------------------------------------- Test Failed. "precice.solverdummy.run.c-fortran" end time: Aug 06 23:35 PDT "precice.solverdummy.run.c-fortran" time elapsed: 00:01:00 ---------------------------------------------------------- End testing: Aug 06 23:35 PDT Solverdummy = 362.19 sec*proc petsc = 2.26 sec*proc