[Insight-developers] [ITK Community] Script for Remote Module testing

[Bradley Lowekamp]

Brian,

The new lhcp-rh6 remote look good to add the the module group. I have these builds configured in debug mode. However, it seems like we are finding more optimization issue that need work around. I intent to add more debugging flags to valid states to many of these builds, at some point.

I have also corrected the name of Linux-x64_64-gcc4.4-m32 to Linux-x64_64-gcc4.4-m32.



On Feb 1, 2014, at 2:30 PM, Brian Helba <brian.helba at kitware.com> wrote:
> 
> To be clear, enabling ITK_BUILD_ALL_MODULES_FOR_TESTS will speed up configuration time.
> 
> However, explicitly setting CTEST_BUILD_TARGET causes the build system to ignore other modules (not strictly required for compilation) anyway, so ITK_BUILD_ALL_MODULES_FOR_TESTS has no effect on build time in this case.

And what controls all the tests that can be run? Something seems off. The new valgrind script here:

http://open.cdash.org/viewNotes.php?buildid=3197008

This script has neither ITK_BUILD_ALL_MODULES_FOR_TESTS enabled nor a CTEST_BUILD_TARGET specified, the test selected to run seem odd:

http://open.cdash.org/viewTest.php?onlypassed&buildid=3197008

They include vnl, but not ITKCore or other dependent ITK modules tests, yet dependent modules tests are being compiled. The configuration is also 2X compared to a normal BUILD_DEFAULT. So why aren't all of them being run?

Just to be clear this is what I was hoping for, but I'm not sure why it's happening this way.

Brad

> 
> Best,
> Brian
>  
> -- 
> Brian Helba
> Medical Imaging
> Kitware, Inc.