Guys, I think this might be a heck of a lot easier than you're making it.<br><br>Just run:<br><br> ctest -T Submit<br><br>I
tried a test of this locally, creating a test group on CDash named
"TestTrack" and running "ctest -D Experimental --track TestTrack"; that
worked. I then temporarily shut down my CDash server (to simulate a
communications problem) and ran a clean dashboard with the same
command. It of course failed to submit.<br>
<br>Finally, after restarting CDash, "ctest -T Submit" just uploaded those last results, without re-building or re-testing anything.<br><br>Ceej<br>aka Chris Hillery<br><br><br><div class="gmail_quote">On Tue, Jun 15, 2010 at 1:11 PM, Larry Procter <span dir="ltr"><<a href="mailto:larry@transpireinc.com">larry@transpireinc.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Thanks for all your help, David. I'll continue my pursuit with a script<br>
I've built for CTest:<br>
<br>
# run this command from the "Testing" subdirectory:<br>
# ctest -VV -S ManualSubmit.cmake<br>
<br>
set (MODEL "Weekly")<br>
set (QUAL_DIR "D:/regress/qual/acurosxb")<br>
set (BUILD_TYPE "RelWithDebInfo_x64")<br>
<br>
set (CTEST_PROJECT_NAME "AcurosXB")<br>
set (CTEST_DROP_METHOD "http")<br>
set (CTEST_DROP_SITE "<a href="http://gluon.transpireinc.com" target="_blank">gluon.transpireinc.com</a>")<br>
set (CTEST_DROP_LOCATION "/CDash/submit.php?project=AcurosXB")<br>
set (CTEST_DROP_SITE_CDASH TRUE)<br>
<br>
find_program(HOSTNAME_CMD NAMES hostname)<br>
exec_program(${HOSTNAME_CMD} OUTPUT_VARIABLE HOSTNAME)<br>
set(CTEST_SITE "${HOSTNAME}")<br>
set(CTEST_BUILD_NAME "RelWithDebInfo_x64")<br>
set(CTEST_DASHBOARD_ROOT<br>
"D:/regress/qual/acurosxb/RelWithDebInfo_x64")<br>
<br>
set (CTEST_SOURCE_DIRECTORY<br>
"d:/regress/qual/acurosxb/RelWithDebInfo_x64/source")<br>
set (CTEST_BINARY_DIRECTORY<br>
"d:/regress/qual/acurosxb/RelWithDebInfo_x64/build")<br>
<div class="im"><br>
ctest_start("${MODEL}" TRACK "${MODEL}")<br>
</div> #ctest_submit(PARTS Submit)<br>
ctest_submit(FILES<br>
"d:/regress/qual/acurosxb/RelWithDebInfo_x64/build/Testing/20100612-0605/update.xml")<br>
ctest_submit(FILES<br>
"d:/regress/qual/acurosxb/RelWithDebInfo_x64/build/Testing/20100612-0605/config.xml")<br>
ctest_submit(FILES<br>
"d:/regress/qual/acurosxb/RelWithDebInfo_x64/build/Testing/20100612-0605/build.xml")<br>
ctest_submit(FILES<br>
"d:/regress/qual/acurosxb/RelWithDebInfo_x64/build/Testing/20100612-0605/test.xml")<br>
<div><div></div><div class="h5"><br>
<br>
<br>
On Tue, 2010-06-15 at 15:31 -0400, David Cole wrote:<br>
> Perhaps if you use model Nightly when you do your weekly builds, you<br>
> would be able to use:<br>
><br>
> ctest -M Nightly -T Submit --track Weekly<br>
><br>
> to do a re-submit, because then, the tag name would be the same for 24<br>
> hours.<br>
><br>
> Is that a possibility?<br>
><br>
><br>
> On Tue, Jun 15, 2010 at 2:55 PM, Larry Procter<br>
> <<a href="mailto:larry@transpireinc.com">larry@transpireinc.com</a>> wrote:<br>
> Unfortunately, this doesn't work because it generates a new<br>
> "tag" which<br>
> doesn't match the name of the subdirectory in which the<br>
> original xml<br>
> files containing the test results exists.<br>
><br>
><br>
><br>
> On Tue, 2010-06-15 at 13:21 -0400, David Cole wrote:<br>
> > If "ctest -M Weekly -T Submit" does not work, then perhaps:<br>
> ><br>
> > ctest -M Experimental -T Submit --track Weekly<br>
> ><br>
> > will work....<br>
> ><br>
> > Let us know if either one works!<br>
> ><br>
> ><br>
> > Thanks,<br>
> > David<br>
> ><br>
> ><br>
> > On Tue, Jun 15, 2010 at 1:20 PM, David Cole<br>
> <<a href="mailto:david.cole@kitware.com">david.cole@kitware.com</a>><br>
> > wrote:<br>
> > make NightlySubmit<br>
> ><br>
> > is equivalent to:<br>
> ><br>
> > ctest -D NightlySubmit<br>
> ><br>
> > and also to:<br>
> ><br>
> > ctest -M Nightly -T Submit<br>
> ><br>
> > I do not know if this will work, because I am not<br>
> 100% certain<br>
> > if ctest cares whether it knows about the -M name or<br>
> not.....<br>
> > but does:<br>
> ><br>
> > ctest -M Weekly -T Submit<br>
> ><br>
> > work?<br>
> ><br>
> ><br>
> > HTH,<br>
> > David<br>
> ><br>
> ><br>
> ><br>
> ><br>
> > On Tue, Jun 15, 2010 at 12:28 PM, Larry Procter<br>
> > <<a href="mailto:larry@transpireinc.com">larry@transpireinc.com</a>> wrote:<br>
> > Thanks Julien.<br>
> ><br>
> > I have already done this, creating a build<br>
> group<br>
> > called "Weekly". In<br>
> > addition, based on information I found on<br>
> the Wiki for<br>
> > running CTest and<br>
> > CDash without CMake<br>
> ><br>
> (<a href="http://public.kitware.com/Wiki/CTest:Using_CTEST_and_CDASH_without_CMAKE" target="_blank">http://public.kitware.com/Wiki/CTest:Using_CTEST_and_CDASH_without_CMAKE</a>).<br>
> > When I run my tests, which require 17 hours<br>
> to<br>
> > complete, everything<br>
> > submits fine and the results show up on the<br>
> dashboard<br>
> > under the "Weekly"<br>
> > group as expected. The issue I need to<br>
> address is how<br>
> > can I manually<br>
> > send the update, build, configure, and test<br>
> "xml"<br>
> > files in the event<br>
> > that the cURL transmission fails? I ask<br>
> this because<br>
> > we occasionally<br>
> > have network issues here and I submit<br>
> manually by<br>
> > running the target<br>
> > platform "make" file, in this case, "nmake<br>
> > NightlySubmit".<br>
> > Unfortunately, there is not target built for<br>
> "Weekly",<br>
> > so I can't use<br>
> > this method.<br>
> ><br>
> > It looks like I may need to reverse-engineer<br>
> the<br>
> > "submit.php" script in<br>
> > the CDash sources and figure out how to feed<br>
> it the<br>
> > correct parameters<br>
> > in the GET string via cURL. I hope not<br>
> though. I<br>
> > would rather learn how<br>
> > to make CMake configure a "WeeklySubmit"<br>
> target.<br>
> ><br>
> > Thanks again,<br>
> ><br>
> > Larry<br>
> ><br>
> ><br>
> > On Tue, 2010-06-15 at 12:06 -0400, Julien<br>
> Jomier<br>
> > wrote:<br>
> > > Larry,<br>
> > ><br>
> > > Look at the wiki:<br>
> > ><br>
> ><br>
> <a href="http://public.kitware.com/Wiki/CDash:Administration#Move_builds_to_another_group" target="_blank">http://public.kitware.com/Wiki/CDash:Administration#Move_builds_to_another_group</a><br>
> > ><br>
> > > Basically, if you are logged in as an<br>
> administrator<br>
> > you can click on<br>
> > > small folder icon and move the build to a<br>
> different<br>
> > group and it will<br>
> > > automatically create a rule for that build<br>
> so any<br>
> > subsequent builds will<br>
> > > be placed in the new group.<br>
> > ><br>
> > > Julien<br>
> > ><br>
> > > On 6/15/2010 11:52 AM, Larry Procter<br>
> wrote:<br>
> > > > Thank you Julien! I am new to this, so<br>
> where can I<br>
> > learn more about<br>
> > > > creating such a rule?<br>
> > > ><br>
> > > > -Larry<br>
> > > ><br>
> > > > On Mon, 2010-06-14 at 20:48 -0400,<br>
> Julien Jomier<br>
> > wrote:<br>
> > > >> rule<br>
> > > ><br>
> > > ><br>
> > ><br>
> ><br>
> ><br>
> _______________________________________________<br>
> > Cdash mailing list<br>
> > <a href="mailto:Cdash@public.kitware.com">Cdash@public.kitware.com</a><br>
> ><br>
> <a href="http://public.kitware.com/cgi-bin/mailman/listinfo/cdash" target="_blank">http://public.kitware.com/cgi-bin/mailman/listinfo/cdash</a><br>
> ><br>
> ><br>
> ><br>
> ><br>
><br>
><br>
><br>
<br>
_______________________________________________<br>
Cdash mailing list<br>
<a href="mailto:Cdash@public.kitware.com">Cdash@public.kitware.com</a><br>
<a href="http://public.kitware.com/cgi-bin/mailman/listinfo/cdash" target="_blank">http://public.kitware.com/cgi-bin/mailman/listinfo/cdash</a><br>
</div></div></blockquote></div><br>