Notes
(0027568) David Cole (manager) 2011-10-12 09:34	What does your CTestConfig file contain? What CDash server are you sending the results to? If you are sending to my.cdash.org then your project will be limited to 10 builds per day with the free-as-in-beer plan. If you are sending to your own CDash server, there is no such limitation.

(0027569) j10171979 (reporter) 2011-10-12 10:38	David, I am not sure if I am sending it to my own CDash. I found multiple CTestConfig.cmake files. The one below is from /var/www/CDash/CDash-1.8.2 Should I change the following line? set(CTEST_DROP_SITE "www.cdash.org") #============================================================================= # CMake - Cross Platform Makefile Generator # Copyright 2000-2009 Kitware, Inc., Insight Software Consortium # # Distributed under the OSI-approved BSD License (the "License"); # see accompanying file Copyright.txt for details. # # This software is distributed WITHOUT ANY WARRANTY; without even the # implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. # See the License for more information. #============================================================================= set(CTEST_PROJECT_NAME "CMake") set(CTEST_NIGHTLY_START_TIME "1:00:00 UTC") set(CTEST_DROP_METHOD "http") set(CTEST_DROP_SITE "www.cdash.org") set(CTEST_DROP_LOCATION "/CDash/submit.php?project=CDash") set(CTEST_DROP_SITE_CDASH TRUE) set(CTEST_CDASH_VERSION "1.6") set(CTEST_CDASH_QUERY_VERSION TRUE)

(0027570) David Cole (manager) 2011-10-12 10:42	That file is from CDash's source tree: if you have access to /var/www/CDash/CDash-1.8.2, then you have your own CDash server. You need to look at the CTestConfig file in your project's source tree (on your own machine, not on the server) to see where ctest will send xml files. What's the URL of the dashboard for your project? Is your source tree publicly available for the project that you're building/testing?

(0027571) j10171979 (reporter) 2011-10-12 13:40	David, The URL is not public, http://servername.company.com/CDash. [^] When I go to the Project dashboard I can see the site (computer name ex. usercomputer.company.name) and build name. I clicked the nightly build name and it lists some paths in my C:/ drive. So what you are saying is that the CTesConfig is save in my hard-drive, correct?

(0027572) David Cole (manager) 2011-10-12 14:00	Yes, that's correct. The CTestConfig.cmake file is in the top level directory in the source tree of your project. On your hard drive.

(0027575) Jeff Lyons (reporter) 2011-10-12 16:35	I think I've found the problem, though I don't know how to solve it. When we submit builds to the experimental dashboard, the builds get tagged with the current system time. A nightly build gets tagged with the ctest parameter “CTEST_NIGHTLY_START_TIME”. Since this tag is the same from run to run, subsequent builds can’t upload to it because there is a pre-existing build with that tag. I’m not sure what to do about this. I think we might be mis-using nightly builds. Is the intent of nightly builds not to fire them up manually? We start builds at night using a cron job, but we've been submitting to the experimental dashboard. We wanted to start submitting them to the nightly dashboard, but if we get duplicate tags this may not be possible.

(0027576) David Cole (manager) 2011-10-12 16:44	That's the way nightly dashboards work. The builds are uniquely tagged by combination of the stamp or tag, plus the build name plus the site name. If you submit more than one nightly dashboard from the same machine with the same build name, then later ones replace the earlier one. This is simply the way "nightly" dashboards work. We only expect you to do a nightly dashboard once a day from any given machine with a given build name. If you must submit multiple ones from the same machine for some reason, then give the later ones different build names.

(0027577) David Cole (manager) 2011-10-12 16:45	See previous notes.

Issue History
Date Modified	Username	Field	Change
2011-10-12 07:50	j10171979	New Issue
2011-10-12 07:50	j10171979	File Added: error log.txt
2011-10-12 07:50	j10171979	File Added: test_win32.VS2008.Debug.T0568_Python_args.r5688_20111011-0400-Nightly_131835327360.18_Build.xml
2011-10-12 07:50	j10171979	File Added: test_win32.VS2008.Debug.T0568_Python_args.r5688_20111011-0400-Nightly_131835327371.59_Configure.xml
2011-10-12 07:50	j10171979	File Added: test_win32.VS2008.Debug.T0568_Python_args.r5688_20111011-0400-Nightly_131835327382_Test.xml
2011-10-12 07:51	j10171979	File Added: test_win32.VS2008.Debug.T0568_Python_args.r5688_20111011-0400-Nightly_131835327394.81_Update.xml
2011-10-12 09:34	David Cole	Note Added: 0027568
2011-10-12 10:38	j10171979	Note Added: 0027569
2011-10-12 10:42	David Cole	Note Added: 0027570
2011-10-12 13:40	j10171979	Note Added: 0027571
2011-10-12 14:00	David Cole	Note Added: 0027572
2011-10-12 16:26	j10171979	File Added: CTestConfig.cmake
2011-10-12 16:26	j10171979	File Added: 20111012-0100.zip
2011-10-12 16:35	Jeff Lyons	Note Added: 0027575
2011-10-12 16:44	David Cole	Note Added: 0027576
2011-10-12 16:44	David Cole	Assigned To	=> David Cole
2011-10-12 16:44	David Cole	Status	new => assigned
2011-10-12 16:45	David Cole	Note Added: 0027577
2011-10-12 16:45	David Cole	Status	assigned => resolved
2011-10-12 16:45	David Cole	Resolution	open => no change required

Relationships