On 10/23/2015 09:10 AM, Nils Gladitz wrote:
I switched from 3.2.1 to 3.4.0-rc2 on a Windows and a Linux dashboard
client for a custom project.
On the Linux client parallel testing now loops with 100% CPU somewhere
in cmCTestMultiProcessHandler::StartNextTests and
cmCTestMultiProcessHandler::CheckOutput.
I reduced it to this test case:
cmake_minimum_required(VERSION 3.4)
project(Foo NONE)
enable_testing()
add_test(NAME foo COMMAND command_not_found)
set_property(TEST foo PROPERTY RUN_SERIAL ON)
add_test(NAME bar COMMAND ${CMAKE_COMMAND} -E echo let_me_run)
The issue seems to exist for sequential ctest runs as well.
The breaking commit seems to be:
07c550caa20d4b1d6ebc08269d744ff6a45c0a6d
cmCTestMultiProcessHandler: Refactor RUN_SERIAL implementation
Nils
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers
