[CMake] CDash submissions show up as two entries, one row for update, one for build/test etc

[Johan Björk]

Attached them with some modifications.

I have one ctest_<platform>.cmake for each platform, that all include
ctest_base.cmake that contains a macro that allow me to run all different
configurations of my builds.

While I have your attention, would it somehow be possible to re-use a single
sourcetree for several builds and still get the (same) update logs for all
builds?

/Johan



On Thu, Jan 13, 2011 at 3:53 PM, David Cole <david.cole at kitware.com> wrote:

> Can you pass along your whole script, and describe how the looping
> works rather than just the snippet you sent...? (Or is that not
> possible for some reason?)
>
> We don't typically run more than one dashboard per script, so you may
> discovered a real problem with trying to run more than one dashboard
> from a single script...
>
> Does this happen only on 2nd and later dashboards in your loop, or
> does even the very 1st one demonstrate this problem?
>
>
> On Thu, Jan 13, 2011 at 9:47 AM, Johan Björk <phb at spotify.com> wrote:
> > Hi David,
> > Not using subprojects.
> > CMake/CTest version 2.8.3 and CDash 1.8.2 (upgraded from the previous
> > release however)
> > /Johan
> >
> >
> > On Thu, Jan 13, 2011 at 3:27 PM, David Cole <david.cole at kitware.com>
> wrote:
> >>
> >> Are subprojects involved? (i.e. -- do you use them and do you have
> >> them set up for this dashboard)
> >>
> >> What versions of CDash and CMake/CTest are you using?
> >>
> >>
> >> On Thu, Jan 13, 2011 at 4:07 AM, Johan Björk <phb at spotify.com> wrote:
> >> > Hi everyone,
> >> > I'm having a strange problem with my CDash submissions, and I'm not
> sure
> >> > what is going on. For every submission I do, I get two builds, one
> that
> >> > only
> >> > has a UPDATE stage, and one line that has the rest of the steps.
> >> > The row with UPDATE has a higher buildID versus the row with
> >> > configure/build/test.
> >> > In my CTest script, I run several builds in a loop. For every build I
> do
> >> > //Setup CTEST_SOURCE_DIRECTORY and CTEST_BINARY_DIRECTORY
> >> >   ctest_start(${CTEST_MODEL})
> >> >   ctest_update()
> >> >   ctest_configure()
> >> >   ctest_build()
> >> >   ctest_test()
> >> >   if (WITH_COVERAGE AND CTEST_COVERAGE_COMMAND)
> >> >     ctest_coverage()
> >> >   endif (WITH_COVERAGE AND CTEST_COVERAGE_COMMAND)
> >> >   if (WITH_MEMCHECK AND CTEST_MEMORYCHECK_COMMAND)
> >> >     ctest_memcheck()
> >> >   endif (WITH_MEMCHECK AND CTEST_MEMORYCHECK_COMMAND)
> >> >   ctest_submit()
> >> >
> >> > I also tried adding the APPEND keyword to the ctest_* commands, but no
> >> > luck.
> >> > Has anyone seen this before? Does anyone have any suggestions how to
> >> > debug
> >> > this?
> >> > Thanks
> >> > /Johan
> >> >
> >> > _______________________________________________
> >> > 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 CMake FAQ at:
> >> > http://www.cmake.org/Wiki/CMake_FAQ
> >> >
> >> > Follow this link to subscribe/unsubscribe:
> >> > http://www.cmake.org/mailman/listinfo/cmake
> >> >
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.cmake.org/pipermail/cmake/attachments/20110113/9dd0ea71/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ctest_base.cmake
Type: application/octet-stream
Size: 3563 bytes
Desc: not available
URL: <http://www.cmake.org/pipermail/cmake/attachments/20110113/9dd0ea71/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ctest_linux.cmake
Type: application/octet-stream
Size: 397 bytes
Desc: not available
URL: <http://www.cmake.org/pipermail/cmake/attachments/20110113/9dd0ea71/attachment-0003.obj>