[CMake] ctest problem

[Andy Cedilnik]

Hi Alex,

When you use scp submit method, you need something on the server side
that will do periodic trigger.
You should really use http submit method.

       Andy

Alex Brooks wrote:

>Hi,
>
>I'm having an issue with setting up ctest.  I previously ran all my
>tests using DashboardManager.tcl (where everything has been working),
>but I wanted some ctest functionality so I tried to switch it over.  I'm
>not having much luck though.
>
>When I try to submit, I get the following:
>
>dash at thistle:build$ ctest -V -D NightlySubmit
>Determine Nightly Start Time
>   Specified time: 13:00:00 PST
>   Get curl time: 1112907600
>   Get the current time: 1112836619
>   Future time, subtract day: 1112821200
>   Current time: 1112836619 Nightly time: 1112821200
>Create new tag: 20050406-2100 - Nightly
>Submit files (using scp)
>  Use HTTP Proxy: www-cache0.usyd.edu.au:8080
>Execute "/usr/bin/scp"
>"/home/dash/cvs/nightly/orca-base/build/Testing/20050406-2100/Test.xml"
>"shell.sourceforge.net:/home/groups/o/or/orca-robotics/incoming/thistle.acfr.usyd.edu.au___CORBA-g++-3.3___20050406-2100-Nightly___XML___Test.xml"
>  Submission successfull
>
>
>However ctest doesn't appear to be trying to hit the cgi trigger
>script.  I modified my trigger script to see if it was being hit, and it
>isn't.  I also used Ethereal to see if any HTTP request was being sent
>out -- it isn't.  Is there any way to get more debugging info out of
>ctest?  Does anyone have any ideas what else to look for?
>
>
>Thanks in advance,
>
>Alex
>
>-----------------------------------------------------------------
>
>In case it helps, here is my ctest script:
>
>#
># Edit this to match your configuration, then set a cron job
># to run it regularly (with 'ctest -S <script_name>').
>#
>SET (HOME "/home/dash")
>
>SET (CTEST_SOURCE_DIRECTORY "${HOME}/cvs/nightly/orca-base")
>SET (CTEST_BINARY_DIRECTORY "${HOME}/cvs/nightly/orca-base/build")
>
>SET (CTEST_CVS_COMMAND "/usr/bin/cvs")
>
># which command to use for running the dashboard
>#
># Note: ensure that we blow away previous installations,
>#       and install after building.
>#
>SET (CTEST_COMMAND
>    "sudo rm -rf /usr/local/include/orca/"
>    "sudo rm -f  /usr/local/lib/libOrca*"
>    "/usr/bin/ctest -D NightlyStart"
>    "/usr/bin/ctest -D NightlyUpdate"
>    "/usr/bin/ctest -D NightlyConfigure"
>    "/usr/bin/ctest -D NightlyBuild"
>    "ls src/tests/patterns"
>    "sudo make install"
>    "/usr/bin/ctest -D NightlyTest"
>    "/usr/bin/ctest -D NightlySubmit"
>)
>
># what cmake command to use for configuring this dashboard
>SET (CTEST_CMAKE_COMMAND "/usr/bin/cmake" )
>
># should ctest wipe the binary tree before running
>SET (CTEST_START_WITH_EMPTY_BINARY_DIRECTORY TRUE)
>
># this is the initial cache to use for the binary tree, be careful to
>escape
># any quotes inside of this string if you use it
>SET (CTEST_INITIAL_CACHE "
>MAKECOMMAND:STRING=make VERBOSE=1
>BUILDNAME:STRING=CORBA-g++-3.3
>SITE:STRING=thistle.acfr.usyd.edu.au
>")
>
># set any extra envionment varibles here
>SET (CTEST_ENVIRONMENT
>CC=/usr/bin/gcc-3.3
>CXX=/usr/bin/g++-3.3
>ORCA_TRANSPORT=CORBA
>HTTP_PROXY=www-cache0.usyd.edu.au
>HTTP_PROXY_PORT=8080
>)
>
>
>
>and my DartConfig.cmake:
>
># Dashboard is opened for submissions for a 24 hour period starting at
># the specified NIGHLY_START_TIME. Time is specified in 24 hour format.
>SET (NIGHTLY_START_TIME "13:00:00 PST")
>
>#
># Dart server to submit results (used by client)
>#
>SET (DROP_METHOD "scp")
>SET (DROP_SITE "shell.sourceforge.net")
>SET (DROP_LOCATION "/home/groups/o/or/orca-robotics/incoming")
>SET (TRIGGER_SITE
>"http://orca-robotics.sourceforge.net/cgi-bin/dart-trigger.pl")
>
># Copy over the orca logo
>CONFIGURE_FILE(${PROJECT_SOURCE_DIR}/doc/images/orca_base_2x3_blue_texture_130.png
>     ${PROJECT_BINARY_DIR}/Testing/HTML/TestingResults/Icons/Logo.gif
>COPYONLY)
>
>SET(DOXYGEN_URL "http://orca-robotics.sourceforge.net/")
>SET(USE_DOXYGEN ON)
>SET(PROJECT_URL "http://orca-robotics.sourceforge.net/")
>
>
>_______________________________________________
>CMake mailing list
>CMake at cmake.org
>http://www.cmake.org/mailman/listinfo/cmake
>  
>


-- 
Andy Cedilnik
Kitware Inc.