[CMake] using ctest launchers leads to empty warning/error messages on the dashboard

2015-07-24 Thread Matthias Kretz
Hi, using set(ENV{CTEST_USE_LAUNCHERS_DEFAULT} "ON") I don't get any output on the CDash dashboard anymore. AFAICT the Build directory in Testing/tag/ is removed but never recreated. I.e. if I call CTEST_LAUNCH_LOGS=./not-existing-directory make the launcher output is not stored to disk.

Re: [CMake] using ctest launchers leads to empty warning/error messages on the dashboard

2015-07-24 Thread Matthias Kretz
On Friday 24 July 2015 10:23:48 Matthias Kretz wrote: > set(ENV{CTEST_USE_LAUNCHERS_DEFAULT} "ON") > > I don't get any output on the CDash dashboard anymore. AFAICT the Build > directory in Testing/tag/ is removed but never recreated. With the following patch I get output back to the dashboard:

Re: [CMake] using ctest launchers leads to empty warning/error messages on the dashboard

2015-07-24 Thread Matthias Kretz
OK, this patch is bogus. Because cmCTestBuildHandler::LaunchHelper::LaunchHelper should call MakeDirectory already if this->Handler->UseCTestLaunch is true. Makes my test results even more strange then. On Friday 24 July 2015 11:28:13 Matthias Kretz wrote: > On Friday 24 July 2015 10:23:48 Matt

Re: [CMake] using ctest launchers leads to empty warning/error messages on the dashboard

2015-07-24 Thread Matthias Kretz
On Friday 24 July 2015 10:23:48 Matthias Kretz wrote: > set(ENV{CTEST_USE_LAUNCHERS_DEFAULT} "ON") > > I don't get any output on the CDash dashboard anymore. AFAICT the Build > directory in Testing/tag/ is removed but never recreated. I.e. if I call Maybe the better lead: I made the UseLauncher

Re: [CMake] using ctest launchers leads to empty warning/error messages on the dashboard

2015-07-24 Thread Nils Gladitz
On 07/24/2015 10:23 AM, Matthias Kretz wrote: set(ENV{CTEST_USE_LAUNCHERS_DEFAULT} "ON") Is that in your ctest -S script? Do you also have set(CTEST_USE_LAUNCHERS ON) in the same script? Nils -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://