Ok. So I finally got the compiler to use more than one thread and the test seems to progress OK until about test # 370 or so where ParaView starts getting launched a bunch of times. Sometimes this works fine and the next test seems to progress and other times it is sitting at an Open File Dialog just waiting. Not sure what I need to do at this point.

Here is my revised CTest script.
cmake_minimum_required ( VERSION 2.6 )

set (CTEST_SITE "[email protected]")
set (CTEST_BUILD_NAME "Rel36-OSX10.5.7-GCC4.0.1(Xcode 3.1)")

get_filename_component(CTEST_DASHBOARD_ROOT "$ {CTEST_SCRIPT_DIRECTORY}/.." ABSOLUTE)
set (CTEST_SOURCE_DIRECTORY "${CTEST_DASHBOARD_ROOT}/ParaView3")
set (CTEST_BINARY_DIRECTORY ${CTEST_SOURCE_DIRECTORY}/Build64)
set (CTEST_UPDATE_COMMAND "/usr/bin/cvs")
set (CTEST_CMAKE_GENERATOR "Unix Makefiles")
set (CTEST_NOTES_FILES
${CTEST_DASHBOARD_ROOT}/ParaView36Dashboard.cmake /tmp/ ParaViewDashBoardNotes-GCC.txt
  ${CTEST_SCRIPT_DIRECTORY}/${CTEST_SCRIPT_NAME}
)
set (CTEST_BUILD_COMMAND     "/usr/bin/make -j16")
set (CTEST_BUILD_FLAGS "-j16")
set (CTEST_BUILD_CONFIGURATION "Debug")
set (CTEST_TIMEOUT "200")

#SET (CTEST_START_WITH_EMPTY_BINARY_DIRECTORY TRUE)
SET (CTEST_UPDATE_OPTIONS "-dAP -r ParaView-3-6")
#ctest_empty_binary_directory (${CTEST_BINARY_DIRECTORY})

ctest_start (Nightly)
ctest_update (SOURCE "${CTEST_DASHBOARD_ROOT}/VTKData")
ctest_update (SOURCE "${CTEST_DASHBOARD_ROOT}/ParaViewData")
ctest_update (SOURCE "${CTEST_SOURCE_DIRECTORY}")

file (WRITE "${CTEST_BINARY_DIRECTORY}/CMakeCache.txt"
"
//Path to a program.
CMAKE_MAKE_PROGRAM:FILEPATH=/usr/bin/make
//Name of generator.
CMAKE_GENERATOR:INTERNAL=Unix Makefiles
//Path to a program.
CVSCOMMAND:FILEPATH=/usr/bin/cvs
//Build type
CMAKE_BUILD_TYPE:STRING=Debug
//Turn on more strict warnings
CMAKE_CXX_FLAGS:STRING=-Wunused -Wformat -Wsign-compare -Wshadow
SITE:STRING=${CTEST_SITE}
BUILDNAME:STRING=${CTEST_BUILD_NAME}
QT_QMAKE_EXECUTABLE:FILEPATH=/Users/Shared/Toolkits/Qt-4.5.1- UBFramework/bin/qmake
CMAKE_BUILD_TYPE:STRING=Debug
BUILD_SHARED_LIBS:BOOL=ON
BUILD_TESTING:BOOL=ON
CMAKE_OSX_ARCHITECTURES:STRING=x86_64
VTK_USE_RPATH:BOOL=ON
VTK_USE_64BIT_IDS:BOOL=ON
VTK_USE_CARBON:BOOL=OFF
VTK_USE_COCOA:BOOL=ON
PARAVIEW_BUILD_PLUGIN_Prism:BOOL=OFF
CMAKE_INSTALL_PREFIX:PATH=/Users/Shared/Toolkits/ParaView-3.6-x64
//Build leak checking support into VTK.
VTK_DEBUG_LEAKS:BOOL=ON
//Path to a data files for ParaView regression tests
PARAVIEW_DATA_ROOT:PATH=/Users/Shared/Kitware-CVS/ParaViewData
//I have to kill timed out tests by brute force for some reason on this machine PV_TEST_CLEAN_COMMAND:STRING=killall -9 pvdataserver pvrenderserver pvserver paraview
//Seems that timeouts in CRS tests are probably the cause of the above.
PARAVIEW_CLIENT_RENDER_SERVER_TESTS:BOOL=OFF
//Build Streaming ParaView Client
PARAVIEW_BUILD_StreamingParaView:BOOL=ON
"
)
ctest_configure (BUILD "${CTEST_BINARY_DIRECTORY}")
ctest_read_custom_files(${CTEST_BINARY_DIRECTORY})
ctest_build (BUILD "${CTEST_BINARY_DIRECTORY}")
ctest_test (BUILD "${CTEST_BINARY_DIRECTORY}" EXCLUDE "GlobalProperties|ColorEditor3|DualSphere")
ctest_submit ()

Thanks
Mike

On Jun 11, 2009, at 4:03 PM, David Cole wrote:

May I recommend:

set (CTEST_NOTES_FILES
${CTEST_DASHBOARD_ROOT}/ParaView36Dashboard.cmake /tmp/ ParaViewDashBoardNotes-GCC.txt
  ${CTEST_SCRIPT_DIRECTORY}/${CTEST_SCRIPT_NAME}
)

That way the script itself is sent as a dashboard note, too.


On Thu, Jun 11, 2009 at 3:50 PM, Michael Jackson <[email protected] > wrote:

Here is my complete script file:

cmake_minimum_required ( VERSION 2.6 )

set (CTEST_SITE "[email protected]")
set (CTEST_BUILD_NAME "Rel36-OSX10.5.7-GCC4.0.1(Xcode 3.1)")

get_filename_component(CTEST_DASHBOARD_ROOT "$ {CTEST_SCRIPT_DIRECTORY}/.." ABSOLUTE)
set (CTEST_SOURCE_DIRECTORY "${CTEST_DASHBOARD_ROOT}/ParaView3")
set (CTEST_BINARY_DIRECTORY ${CTEST_SOURCE_DIRECTORY}/Build64)
set (CTEST_UPDATE_COMMAND "/usr/bin/cvs")
set (CTEST_CMAKE_GENERATOR "Unix Makefiles")
set (CTEST_NOTES_FILES ${CTEST_DASHBOARD_ROOT}/ ParaView36Dashboard.cmake /tmp/ParaViewDashBoardNotes-GCC.txt)

set (CTEST_BUILD_COMMAND     "/usr/bin/make")

set (CTEST_BUILD_FLAGS -j16)
set (CTEST_BUILD_CONFIGURATION "Debug")
set (CTEST_TIMEOUT "200")

SET (CTEST_START_WITH_EMPTY_BINARY_DIRECTORY FALSE)
SET (CTEST_UPDATE_OPTIONS "-dAP -r ParaView-3-6")
#ctest_empty_binary_directory (${CTEST_BINARY_DIRECTORY})

ctest_start (Nightly)
ctest_update (SOURCE "${CTEST_DASHBOARD_ROOT}/VTKData")
ctest_update (SOURCE "${CTEST_DASHBOARD_ROOT}/ParaViewData")
ctest_update (SOURCE "${CTEST_SOURCE_DIRECTORY}")


file (WRITE "${CTEST_BINARY_DIRECTORY}/CMakeCache.txt"
"
//Path to a program.
CMAKE_MAKE_PROGRAM:FILEPATH=/usr/bin/make
//Name of generator.
CMAKE_GENERATOR:INTERNAL=Unix Makefiles
//Path to a program.
CVSCOMMAND:FILEPATH=/usr/bin/cvs
//Build type
CMAKE_BUILD_TYPE:STRING=Debug
//Turn on more strict warnings
CMAKE_CXX_FLAGS:STRING=-Wunused -Wformat -Wsign-compare -Wshadow
SITE:STRING=${CTEST_SITE}
BUILDNAME:STRING=${CTEST_BUILD_NAME}
QT_QMAKE_EXECUTABLE:FILEPATH=/Users/Shared/Toolkits/Qt-4.5.1- UBFramework/bin/qmake
CMAKE_BUILD_TYPE:STRING=Debug
BUILD_SHARED_LIBS:BOOL=ON
BUILD_TESTING:BOOL=ON
CMAKE_OSX_ARCHITECTURES:STRING=x86_64
VTK_USE_RPATH:BOOL=ON
VTK_USE_64BIT_IDS:BOOL=ON
VTK_USE_CARBON:BOOL=OFF
VTK_USE_COCOA:BOOL=ON
PARAVIEW_BUILD_PLUGIN_Prism:BOOL=OFF
CMAKE_INSTALL_PREFIX:PATH=/Users/Shared/Toolkits/ParaView-3.6-x64
"
)
ctest_configure (BUILD "${CTEST_BINARY_DIRECTORY}")
ctest_read_custom_files(${CTEST_BINARY_DIRECTORY})
ctest_build (BUILD "${CTEST_BINARY_DIRECTORY}")
ctest_test (BUILD "${CTEST_BINARY_DIRECTORY}" EXCLUDE "GlobalProperties|ColorEditor3|DualSphere")
ctest_submit ()


_________________________________________________________
Mike Jackson                  [email protected]


On Jun 11, 2009, at 3:47 PM, David Cole wrote:

set(CTEST_BUILD_FLAGS -j16)


_______________________________________________
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 ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview

Reply via email to