[CMake] Using CTest without DART??

Fri Jun 4 12:32:39 EDT 2010

We do have a CTestConfig.cmake:

set(CTEST_PROJECT_NAME "BRAINS3")
set(CTEST_NIGHTLY_START_TIME "00:00:00 EST")
set(CTEST_DROP_METHOD "http")
set(CTEST_DROP_SITE "testing.psychiatry.uiowa.edu")
set(CTEST_DROP_LOCATION "/CDash/submit.php?project=BRAINS3")
set(CTEST_DROP_SITE_CDASH TRUE)

I ran the ctest command with --debug and the reason it still wants to
use DartConfiguration.tcl is that it can't find
CTestConfiguration.ini.  How is CTestConfiguration.ini generated?  Why
don't I have one?

On Fri, Jun 4, 2010 at 10:55 AM, David Cole <david.cole at kitware.com> wrote:
> What are the contents of your CTestConfig.cmake file?
> If you are going to run dashboards like this:
> BUILD COMMAND runcmd ctest -V -D NightlyStart -D NightlyConfigure -D
> NightlyBuild -D NightlyTest -D NightlySubmit
> running: ctest -V -D NightlyStart -D NightlyConfigure -D NightlyBuild
> -D NightlyTest -D NightlySubmit
> Then when you configure, you will have to define BUILDNAME and SITE
> variables so that the build name and site are known somehow. Our typical
> dashboard runs that we do nowadays all use -S scripts with those things set
> in the script. But to run a dashboard with ctest -D args, you have to cache
> any necessary information that would otherwise be set in the driving script.
>
> Hope this helps,
> David
>
> On Fri, Jun 4, 2010 at 11:25 AM, kent williams <nkwmailinglists at gmail.com>
> wrote:
>>
>> I'm now finding out that we had
>>
>> include(Dart)
>>
>> in all our Makefiles.  I commented that out, and added
>>
>> include(CTest)
>>
>> instead. Then I deleted everything in the build directory, and
>> re-configured.  I get these errors still:
>>
>>
>> /scratch/williamsnk/Testing/BRAINS-COMPILE/Linux/DEBUG-lib/CMake-build/bin/cmake
>> -GKDevelop3 -DCMAKE_CXX_COMPILER:FILEPATH=/usr/bin/g++
>> {-DCMAKE_CXX_FLAGS:STRING=-m32 -UNDEBUG -g
>> -UITKIO_DEPRECATED_METADATA_ORIENTATION  -Wall -W -Wcast-qual
>> -Wwrite-strings } {-DCMAKE_CXX_FLAGS_RELEASE:STRING=-m32 -UNDEBUG -g
>> -UITKIO_DEPRECATED_METADATA_ORIENTATION  -Wall -W -Wcast-qual
>> -Wwrite-strings } {-DCMAKE_CXX_FLAGS_DEBUG:STRING=-m32 -UNDEBUG -g
>> -UITKIO_DEPRECATED_METADATA_ORIENTATION  -Wall -W -Wcast-qual
>> -Wwrite-strings } -DCMAKE_C_COMPILER:FILEPATH=/usr/bin/gcc
>> {-DCMAKE_C_FLAGS:STRING=-m32 -UNDEBUG -g
>> -UITKIO_DEPRECATED_METADATA_ORIENTATION  -Wall -W -Wcast-qual
>> -Wwrite-strings } {-DCMAKE_Fortran_FLAGS:STRING=-m32 -UNDEBUG -g
>> -UITKIO_DEPRECATED_METADATA_ORIENTATION  -Wall -W -Wcast-qual
>> -Wwrite-strings } -DDART_TESTING_TIMEOUT:STRING=600
>>
>> {-DMEMORYCHECK_COMMAND_OPTIONS:STRING=--suppressions=/scratch/williamsnk/Testing/BRAINS3/BuildScripts/ValgrindSuppression.supp
>> --verbose --num-callers=40 --leak-check=full --leak-resolution=high
>> --show-reachable=yes} -DMEMORYCHECK_COMMAND:PATH=/usr/bin/valgrind
>> -DCMAKE_SHARED_LINKER_FLAGS:STRING= -DCMAKE_EXE_LINKER_FLAGS:STRING=
>> -DCMAKE_MODULE_LINKER_FLAGS:STRING= -DSITE:STRING=compute6.uiowa
>> -DBUILDNAME:STRING=Linux.DEBUG
>> -DOPENGL_gl_LIBRARY:FILEPATH=/usr/lib/libGL.so
>> -DOPENGL_glu_LIBRARY:FILEPATH=/usr/lib/libGLU.so
>> -DOPENGL_INCLUDE_DIR:PATH=/usr/include -DCMAKE_BUILD_TYPE=Debug
>> -DMAKECOMMAND:STRING=make -j 4
>>
>> -DITK_DIR:FILEPATH=/scratch/williamsnk/Testing/BRAINS-COMPILE/Linux/DEBUG-build/lib/InsightToolkit
>>
>> -DKWWidgets_DIR:FILEPATH=/scratch/williamsnk/Testing/BRAINS-COMPILE/Linux/DEBUG-build/lib/KWWidgets
>>
>> -DVTK_DIR:FILEPATH=/scratch/williamsnk/Testing/BRAINS-COMPILE/Linux/DEBUG-build/lib/vtk-5.6
>>
>> -DCMAKE_INSTALL_PREFIX:PATH=/scratch/williamsnk/Testing/BRAINS-COMPILE/Linux/DEBUG-build
>> -DCPACK_GENERATOR:STRING=TGZ
>> -DCPACK_PACKAGE_FILE_NAME:STRING=BRAINS3-3.3-alpha-2010-06-04-linux-x86
>> -DUSE_OLD_BUILD:BOOL=OFF -DBRAINS_BUILD_TESTING:BOOL=ON
>>
>> -DBRAINS_BINARY_DIR:PATH=/scratch/williamsnk/Testing/BRAINS-COMPILE/Linux/DEBUG-build
>> -DDISABLE_ITK_TESTING:BOOL=ON -DDISABLE_ALT_DICOM_FILTERS:BOOL=ON
>> -DUSE_GUI:BOOL=OFF -DENABLE_TEST_IN_GUI_MODE:BOOL=OFF
>> -DUSE_BRAINS_BETA:BOOL=ON -DUSE_BRAINS_ALPHA:BOOL=ON
>> -DCMAKE_SKIP_RPATH:BOOL=ON -DUSE_PYTHON:BOOL=OFF -DUSE_TCL:BOOL=ON
>>
>> -DWrapITK_DIR:PATH=/scratch/williamsnk/Testing/BRAINS-COMPILE/Linux/DEBUG-lib/Insight-build/Wrapping/WrapITK
>> -DINSTALL_DEVEL_FILES:BOOL=ON -DBUILD_SHARED_LIBS:BOOL=ON
>>
>> -DTCL_INCLUDE_PATH:PATH=/scratch/williamsnk/Testing/BRAINS-COMPILE/Linux/DEBUG-lib/tcl-build/include
>>
>> -DTCL_LIBRARY:FILEPATH=/scratch/williamsnk/Testing/BRAINS-COMPILE/Linux/DEBUG-build/lib/libtcl8.5.so
>>
>> -DTK_INCLUDE_PATH:PATH=/scratch/williamsnk/Testing/BRAINS-COMPILE/Linux/DEBUG-lib/tcl-build/include
>>
>> -DTK_LIBRARY:FILEPATH=/scratch/williamsnk/Testing/BRAINS-COMPILE/Linux/DEBUG-build/lib/libtk8.5.so
>>
>> -DvtkINRIA3D_DIR:PATH=/scratch/williamsnk/Testing/BRAINS-COMPILE/Linux/DEBUG-build/lib
>> -DNITRC_Standalone:BOOL=ON -DUSE_DEBUG_IMAGE_VIEWER:BOOL=ON
>>
>> -DCMAKE_RUNTIME_OUTPUT_DIRECTORY:PATH=/scratch/williamsnk/Testing/BRAINS-COMPILE/Linux/DEBUG-build/bin
>>
>> -DCMAKE_LIBRARY_OUTPUT_DIRECTORY:PATH=/scratch/williamsnk/Testing/BRAINS-COMPILE/Linux/DEBUG-build/lib
>>
>> -DCMAKE_ARCHIVE_OUTPUT_DIRECTORY:PATH=/scratch/williamsnk/Testing/BRAINS-COMPILE/Linux/DEBUG-build/lib
>> /scratch/williamsnk/Testing/BRAINS3/../BRAINS3
>> -- The C compiler identification is GNU
>> -- The CXX compiler identification is GNU
>> -- Check for working C compiler: /usr/bin/gcc
>> -- Check for working C compiler: /usr/bin/gcc -- works
>> -- Detecting C compiler ABI info
>> -- Detecting C compiler ABI info - done
>> -- Check for working CXX compiler: /usr/bin/g++
>> -- Check for working CXX compiler: /usr/bin/g++ -- works
>> -- Detecting CXX compiler ABI info
>> -- Detecting CXX compiler ABI info - done
>> -- Configuring done
>> -- Generating done
>> -- Build files have been written to:
>> /scratch/williamsnk/Testing/BRAINS-COMPILE/Linux/DEBUG-build/BRAINS3-build
>>
>> -------------------BUILD_DASHBOARD---------------------
>> BUILD COMMAND runcmd ctest -V -D NightlyStart -D NightlyConfigure -D
>> NightlyBuild -D NightlyTest -D NightlySubmit
>> running: ctest -V -D NightlyStart -D NightlyConfigure -D NightlyBuild
>> -D NightlyTest -D NightlySubmit
>> UpdateCTestConfiguration  from
>>
>> :/scratch/williamsnk/Testing/BRAINS-COMPILE/Linux/DEBUG-build/BRAINS3-build/src-build/DartConfiguration.tcl
>> Cannot find file:
>>
>> /scratch/williamsnk/Testing/BRAINS-COMPILE/Linux/DEBUG-build/BRAINS3-build/src-build/DartConfiguration.tcl
>>   Site:
>>   Build name:
>> WARNING: No nightly start time found please set in CTestConfig.cmake
>> or DartConfig.cmake
>> Problem initializing the dashboard.
>>
>> child process exited abnormally
>>
>> Results:
>> build of "Experimental" failed
>>
>> Compilation finished at Fri Jun  4 10:21:12
>>
>>
>> On Fri, Jun 4, 2010 at 9:59 AM, David Cole <david.cole at kitware.com> wrote:
>> > Are you doing:
>> > include(CTest)
>> > in your CMakeLists.txt file?
>> >
>> > On Fri, Jun 4, 2010 at 10:51 AM, kent williams
>> > <nkwmailinglists at gmail.com>
>> > wrote:
>> >>
>> >> We don't have Dart installed on some machines we want to do testing
>> >> on. Consequently including Dart.cmake does nothing to generate
>> >> DartConfiguration.tcl.
>> >>
>> >> If you're not using Dart, how do you set things up such that you avoid
>> >> this error?
>> >>
>> >> running: ctest -V -D NightlyStart -D NightlyConfigure -D NightlyBuild
>> >> -D NightlyTest -D NightlySubmit
>> >> UpdateCTestConfiguration  from
>> >>
>> >>
>> >> :/scratch/williamsnk/Testing/BRAINS-COMPILE/Linux/FAST-build/BRAINS3-build/src-build/DartConfiguration.tcl
>> >> Cannot find file:
>> >>
>> >>
>> >> /scratch/williamsnk/Testing/BRAINS-COMPILE/Linux/FAST-build/BRAINS3-build/src-build/DartConfiguration.tcl
>> >>   Site:
>> >>   Build name:
>> >> WARNING: No nightly start time found please set in CTestConfig.cmake
>> >> or DartConfig.cmake
>> >> Problem initializing the dashboard.
>> >> _______________________________________________
>> >> Powered by www.kitware.com
>> >>
>> >> Visit other Kitware open-source projects at
>> >> http://www.kitware.com/opensource/opensource.html
>> >>
>> >> Please keep messages on-topic and check the CMake FAQ at:
>> >> http://www.cmake.org/Wiki/CMake_FAQ
>> >>
>> >> Follow this link to subscribe/unsubscribe:
>> >> http://www.cmake.org/mailman/listinfo/cmake
>> >
>> >
>
>