kolan
/
CMake
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
CMake/Tests/CMakeTests/ProcessorCountTest.cmake.in

80 lines
2.3 KiB
CMake
Raw Normal View History

Add module ProcessorCount.cmake (#11302) Credit goes to David Cole ( http://www.kitware.com/blog/home/post/63 ). Also add a script-based test of the new module. Signed-off-by: Michael Wild <themiwi@users.sourceforge.net>
2010-10-08 11:16:04 +04:00
include(ProcessorCount)
ProcessorCount(processor_count)
ProcessorCount: Use ERROR_QUIET with execute_process (#11302) Also, comment out all "debugging" calls to message() that helped us interpret the output on other platforms when running on the dashboard clients. Using ERROR_QUIET avoids unnecessary stderr output while calling external tools to determine the processor count. If there's an error parsing the output, we set the count to 0 anyhow. Also, the test will fail on a CMake dashboard run if the count comes back equal to 0. Now that the code is "done"-ish, remove the debugging output. Expect no output on stdout or stderr when calling the ProcessorCount function from now on.
2011-03-18 21:28:24 +03:00
message("### 1. This line should be the first line of text in the test output.")
message("### 2. If there was output from this test before line #1, then the")
message("### 3. ProcessorCount(...) function call is emitting output that it shouldn't...")
Add module ProcessorCount.cmake (#11302) Credit goes to David Cole ( http://www.kitware.com/blog/home/post/63 ). Also add a script-based test of the new module. Signed-off-by: Michael Wild <themiwi@users.sourceforge.net>
2010-10-08 11:16:04 +04:00
message("processor_count='${processor_count}'")
Compare ProcessorCount to SystemInformation count. (#11302) Maximize output to gather data on the dashboards. Only FATAL_ERROR out once at the bottom if an error occurred earlier.
2010-11-09 22:29:52 +03:00
execute_process(
ProcessorCount test: fix path to cmsysTestsCxx executable Use a generator expression to get the real place of this target instead of guessing it wrong.
2013-01-25 02:15:13 +04:00
COMMAND "${KWSYS_TEST_EXE}"
Compare ProcessorCount to SystemInformation count. (#11302) Maximize output to gather data on the dashboards. Only FATAL_ERROR out once at the bottom if an error occurred earlier.
2010-11-09 22:29:52 +03:00
testSystemInformation
ProcessorCount: Use ERROR_QUIET with execute_process (#11302) Also, comment out all "debugging" calls to message() that helped us interpret the output on other platforms when running on the dashboard clients. Using ERROR_QUIET avoids unnecessary stderr output while calling external tools to determine the processor count. If there's an error parsing the output, we set the count to 0 anyhow. Also, the test will fail on a CMake dashboard run if the count comes back equal to 0. Now that the code is "done"-ish, remove the debugging output. Expect no output on stdout or stderr when calling the ProcessorCount function from now on.
2011-03-18 21:28:24 +03:00
OUTPUT_VARIABLE tsi_out
ProcessorCount test: require SystemInformation process to work Currently this silently fails on some systems. Make sure those things get noticed so we can fix that.
2013-01-23 23:23:18 +04:00
ERROR_VARIABLE tsi_err
RESULT_VARIABLE tsi_res
)
if (tsi_res)
message("executing \"${KWSYS_TEST_EXE}\" failed")
message(FATAL_ERROR "output: ${tsi_res}")
endif ()
Compare ProcessorCount to SystemInformation count. (#11302) Maximize output to gather data on the dashboards. Only FATAL_ERROR out once at the bottom if an error occurred earlier.
2010-11-09 22:29:52 +03:00
string(REGEX REPLACE "(.*)GetNumberOfPhysicalCPU:.([0-9]*)(.*)" "\\2"
ProcessorCount: Use ERROR_QUIET with execute_process (#11302) Also, comment out all "debugging" calls to message() that helped us interpret the output on other platforms when running on the dashboard clients. Using ERROR_QUIET avoids unnecessary stderr output while calling external tools to determine the processor count. If there's an error parsing the output, we set the count to 0 anyhow. Also, the test will fail on a CMake dashboard run if the count comes back equal to 0. Now that the code is "done"-ish, remove the debugging output. Expect no output on stdout or stderr when calling the ProcessorCount function from now on.
2011-03-18 21:28:24 +03:00
system_info_processor_count "${tsi_out}")
ProcessorCount test: more output, do not fail. (#11302) More dev work remains to be done here. Removing test failure condition until that dev work is complete, so it does not mask or hide other, more important failures, on the dashboard.
2010-11-10 18:23:50 +03:00
Compare ProcessorCount to SystemInformation count. (#11302) Maximize output to gather data on the dashboards. Only FATAL_ERROR out once at the bottom if an error occurred earlier.
2010-11-09 22:29:52 +03:00
message("system_info_processor_count='${system_info_processor_count}'")
if(system_info_processor_count EQUAL processor_count)
message("processor count matches system information")
Add ProcessorCount support for QNX via pidin. (#11302) Thanks to Rolf Eike Beer <eike@sf-mail.de> for the code snippet parsing the pidin output.
2010-11-08 17:37:04 +03:00
endif()
ProcessorCount test: more output, do not fail. (#11302) More dev work remains to be done here. Removing test failure condition until that dev work is complete, so it does not mask or hide other, more important failures, on the dashboard.
2010-11-10 18:23:50 +03:00
message("")
message("CTEST_FULL_OUTPUT (Avoid ctest truncation of output)")
message("")
ProcessorCount: Use ERROR_QUIET with execute_process (#11302) Also, comment out all "debugging" calls to message() that helped us interpret the output on other platforms when running on the dashboard clients. Using ERROR_QUIET avoids unnecessary stderr output while calling external tools to determine the processor count. If there's an error parsing the output, we set the count to 0 anyhow. Also, the test will fail on a CMake dashboard run if the count comes back equal to 0. Now that the code is "done"-ish, remove the debugging output. Expect no output on stdout or stderr when calling the ProcessorCount function from now on.
2011-03-18 21:28:24 +03:00
message("tsi_out='${tsi_out}'")
message("tsi_err='${tsi_err}'")
ProcessorCount test: more output, do not fail. (#11302) More dev work remains to be done here. Removing test failure condition until that dev work is complete, so it does not mask or hide other, more important failures, on the dashboard.
2010-11-10 18:23:50 +03:00
message("")
Compare ProcessorCount to SystemInformation count. (#11302) Maximize output to gather data on the dashboards. Only FATAL_ERROR out once at the bottom if an error occurred earlier.
2010-11-09 22:29:52 +03:00
# Evaluate possible error conditions:
#
set(err 0)
ProcessorCount: Test fails if count is 0 (#11302) It also fails if count is not a decimal integer.
2011-03-10 00:21:10 +03:00
set(fatal 0)
Compare ProcessorCount to SystemInformation count. (#11302) Maximize output to gather data on the dashboards. Only FATAL_ERROR out once at the bottom if an error occurred earlier.
2010-11-09 22:29:52 +03:00
Add module ProcessorCount.cmake (#11302) Credit goes to David Cole ( http://www.kitware.com/blog/home/post/63 ). Also add a script-based test of the new module. Signed-off-by: Michael Wild <themiwi@users.sourceforge.net>
2010-10-08 11:16:04 +04:00
if(processor_count EQUAL 0)
Compare ProcessorCount to SystemInformation count. (#11302) Maximize output to gather data on the dashboards. Only FATAL_ERROR out once at the bottom if an error occurred earlier.
2010-11-09 22:29:52 +03:00
set(err 1)
ProcessorCount: Test fails if count is 0 (#11302) It also fails if count is not a decimal integer.
2011-03-10 00:21:10 +03:00
set(fatal 1)
ProcessorCount test: more output, do not fail. (#11302) More dev work remains to be done here. Removing test failure condition until that dev work is complete, so it does not mask or hide other, more important failures, on the dashboard.
2010-11-10 18:23:50 +03:00
message("err 1")
Compare ProcessorCount to SystemInformation count. (#11302) Maximize output to gather data on the dashboards. Only FATAL_ERROR out once at the bottom if an error occurred earlier.
2010-11-09 22:29:52 +03:00
message("could not determine number of processors
Add ProcessorCount support for QNX via pidin. (#11302) Thanks to Rolf Eike Beer <eike@sf-mail.de> for the code snippet parsing the pidin output.
2010-11-08 17:37:04 +03:00
- Additional code for this platform needed in ProcessorCount.cmake?")
ProcessorCount test: more output, do not fail. (#11302) More dev work remains to be done here. Removing test failure condition until that dev work is complete, so it does not mask or hide other, more important failures, on the dashboard.
2010-11-10 18:23:50 +03:00
message("")
Add module ProcessorCount.cmake (#11302) Credit goes to David Cole ( http://www.kitware.com/blog/home/post/63 ). Also add a script-based test of the new module. Signed-off-by: Michael Wild <themiwi@users.sourceforge.net>
2010-10-08 11:16:04 +04:00
endif()
Compare ProcessorCount to SystemInformation count. (#11302) Maximize output to gather data on the dashboards. Only FATAL_ERROR out once at the bottom if an error occurred earlier.
2010-11-09 22:29:52 +03:00
if(NOT system_info_processor_count EQUAL processor_count)
set(err 2)
ProcessorCount test: more output, do not fail. (#11302) More dev work remains to be done here. Removing test failure condition until that dev work is complete, so it does not mask or hide other, more important failures, on the dashboard.
2010-11-10 18:23:50 +03:00
message("err 2")
Compare ProcessorCount to SystemInformation count. (#11302) Maximize output to gather data on the dashboards. Only FATAL_ERROR out once at the bottom if an error occurred earlier.
2010-11-09 22:29:52 +03:00
message("SystemInformation and ProcessorCount.cmake disagree:\n"
"processor_count='${processor_count}'\n"
"SystemInformation processor_count='${system_info_processor_count}'")
ProcessorCount test: more output, do not fail. (#11302) More dev work remains to be done here. Removing test failure condition until that dev work is complete, so it does not mask or hide other, more important failures, on the dashboard.
2010-11-10 18:23:50 +03:00
message("")
Compare ProcessorCount to SystemInformation count. (#11302) Maximize output to gather data on the dashboards. Only FATAL_ERROR out once at the bottom if an error occurred earlier.
2010-11-09 22:29:52 +03:00
endif()
if(NOT processor_count MATCHES "^[0-9]+$")
set(err 3)
ProcessorCount: Test fails if count is 0 (#11302) It also fails if count is not a decimal integer.
2011-03-10 00:21:10 +03:00
set(fatal 1)
ProcessorCount test: more output, do not fail. (#11302) More dev work remains to be done here. Removing test failure condition until that dev work is complete, so it does not mask or hide other, more important failures, on the dashboard.
2010-11-10 18:23:50 +03:00
message("err 3")
Compare ProcessorCount to SystemInformation count. (#11302) Maximize output to gather data on the dashboards. Only FATAL_ERROR out once at the bottom if an error occurred earlier.
2010-11-09 22:29:52 +03:00
message("ProcessorCount function returned a non-integer")
ProcessorCount test: more output, do not fail. (#11302) More dev work remains to be done here. Removing test failure condition until that dev work is complete, so it does not mask or hide other, more important failures, on the dashboard.
2010-11-10 18:23:50 +03:00
message("")
Compare ProcessorCount to SystemInformation count. (#11302) Maximize output to gather data on the dashboards. Only FATAL_ERROR out once at the bottom if an error occurred earlier.
2010-11-09 22:29:52 +03:00
endif()
if(NOT system_info_processor_count MATCHES "^[0-9]+$")
set(err 4)
ProcessorCount test: more output, do not fail. (#11302) More dev work remains to be done here. Removing test failure condition until that dev work is complete, so it does not mask or hide other, more important failures, on the dashboard.
2010-11-10 18:23:50 +03:00
message("err 4")
Compare ProcessorCount to SystemInformation count. (#11302) Maximize output to gather data on the dashboards. Only FATAL_ERROR out once at the bottom if an error occurred earlier.
2010-11-09 22:29:52 +03:00
message("SystemInformation ProcessorCount function returned a non-integer")
ProcessorCount test: more output, do not fail. (#11302) More dev work remains to be done here. Removing test failure condition until that dev work is complete, so it does not mask or hide other, more important failures, on the dashboard.
2010-11-10 18:23:50 +03:00
message("")
Compare ProcessorCount to SystemInformation count. (#11302) Maximize output to gather data on the dashboards. Only FATAL_ERROR out once at the bottom if an error occurred earlier.
2010-11-09 22:29:52 +03:00
endif()
ProcessorCount: Test fails if count is 0 (#11302) It also fails if count is not a decimal integer.
2011-03-10 00:21:10 +03:00
if(fatal)
message(FATAL_ERROR "processor_count='${processor_count}' - see previous test output for more details - it is likely more/different code is needed in ProcessorCount.cmake to fix this test failure - processor_count should be a non-zero positive integer (>=1) for all supported CMake platforms")
Compare ProcessorCount to SystemInformation count. (#11302) Maximize output to gather data on the dashboards. Only FATAL_ERROR out once at the bottom if an error occurred earlier.
2010-11-09 22:29:52 +03:00
endif()