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