It is fairly stable. When in doubt, just check CDash's dashboard itself: <a href="http://www.cdash.org/CDash/index.php?project=CDash">http://www.cdash.org/CDash/index.php?project=CDash</a><div><br></div><div>We have two failing tests that we are working on fixing. And we have been adding tests over the last few months to get better coverage on the nightly test suite. Overall, I would say svn trunk is actually in better shape than the 1-6 branch at this point in time. (Because it is fairly stable and there are a handful of bug fixes like this one that are in it...)</div>
<div><br></div><div>Let us know how it turns out.</div><div><br></div><div>Thanks,</div><div>David</div><div><br></div><div><br><div class="gmail_quote">On Tue, Aug 17, 2010 at 5:47 AM, O'Shea, David <span dir="ltr"><<a href="mailto:OShea.D@emsglobaltracking.com">OShea.D@emsglobaltracking.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div>
<div dir="ltr" align="left"><span><font color="#0000ff" size="2" face="Arial">Hi David,</font></span></div>
<div dir="ltr" align="left"><span><font color="#0000ff" size="2" face="Arial"></font></span> </div>
<div dir="ltr" align="left"><span><font color="#0000ff" size="2" face="Arial">Thanks for your response and suggested workaround! With
regards to using an SVN trunk installation of CDash, that is
possible. I don't want to annoy our IT administrator too much, though, so
is it fairly stable?</font></span></div>
<div dir="ltr" align="left"><span><font color="#0000ff" size="2" face="Arial"></font></span> </div>
<div dir="ltr" align="left"><span><font color="#0000ff" size="2" face="Arial">Regards,</font></span></div>
<div dir="ltr" align="left"><span><font color="#0000ff" size="2" face="Arial">David</font></span></div>
<div><font color="#0000ff" size="2" face="Arial"></font> </div>
<div><font color="#0000ff" size="2" face="Arial"></font> </div><br>
<blockquote style="border-left:#0000ff 2px solid;padding-left:5px;margin-left:5px;margin-right:0px">
<div dir="ltr" lang="en-us" align="left">
<hr>
<font size="2" face="Tahoma"><b>From:</b> David Cole
[mailto:<a href="mailto:david.cole@kitware.com" target="_blank">david.cole@kitware.com</a>] <br><b>Sent:</b> Tuesday, 17 August 2010 12:33
AM<br><b>To:</b> O'Shea, David<br><b>Cc:</b>
<a href="mailto:cdash@public.kitware.com" target="_blank">cdash@public.kitware.com</a><br><b>Subject:</b> Re: [Cdash] Dashboard view only
shows last build with APPEND, but build page shows both<br></font><br></div><div><div></div><div class="h5">
<div></div>
<div class="gmail_quote">On Mon, Aug 16, 2010 at 11:00 AM, David Cole <span dir="ltr"><<a href="mailto:david.cole@kitware.com" target="_blank">david.cole@kitware.com</a>></span>
wrote:<br>
<blockquote style="border-left:#ccc 1px solid;margin:0px 0px 0px 0.8ex;padding-left:1ex" class="gmail_quote">
<div class="gmail_quote">
<div>
<div></div>
<div>On Fri, Aug 13, 2010 at 12:42 AM, O'Shea, David <span dir="ltr"><<a href="mailto:OShea.D@emsglobaltracking.com" target="_blank">OShea.D@emsglobaltracking.com</a>></span> wrote:<br>
<blockquote style="border-left:#ccc 1px solid;margin:0px 0px 0px 0.8ex;padding-left:1ex" class="gmail_quote">Hi all,<br><br>I'm using 'ctest -S' to run a script
which performs configure, build<br>('make all'), test, coverage, and then
an additional build ('make<br>doc'), and submitting the result to CDash
1.6.4.<br><br>Here is what I think is the "interesting" part of the
script:<br><br>>>><br>ctest_empty_binary_directory(${CTEST_BINARY_DIRECTORY})<br>ctest_start("Experimental")<br>ctest_configure(OPTIONS
[...])<br>ctest_read_custom_files(${CTEST_BINARY_DIRECTORY})<br>ctest_build(APPEND)<br>#
tried with and without "APPEND" in ctest_build()
above<br>ctest_test()<br>ctest_coverage()<br><br>set(CTEST_NOTES_FILES<br>
[...])<br><br>ctest_submit()<br><br>ctest_start("Experimental"
APPEND)<br># tried with and without the additional call to ctest_start()
above<br>ctest_build(TARGET "doc"<br>
APPEND)<br>ctest_submit(PARTS Build)<br><<<<br><br>For the
purposes of my test, I've made the first ctest_build() report<br>1 warning
plus 2 errors, and the second ctest_build() report
4<br>warnings.<br><br>The issue I'm having is that, after the first
ctest_submit(), the main<br>dashboard page in CDash shows in the "Build"
columns the warnings and<br>errors from the first ctest_build() (1 warning
plus 2 errors), but<br>once the second ctest_submit() has been executed,
only the results of<br>the second ctest_build() are shown (0 errors and 4
warnings).<br><br>When I click on the build name in the "Build Name"
column to see the<br>details of the build, in the "Current Build" table,
it shows the total<br>errors (2) and warnings (5), which is what I'd
expect to see on the<br>main dashboard page.<br><br>I assume this is a
bug, and not by design?<br></blockquote>
<div><br></div>
<div><br></div></div></div>
<div>Correct -- this *was* a bug in CDash. I know the fix was committed to
svn trunk of CDash within the past several weeks. Is there any way you can
try this scenario with an "svn trunk" installation of CDash, or do you not
have control over the CDash server...?</div>
<div><br></div>
<div>It should be fixed in svn trunk of CDash, and in the next official
release (1.8, sometime later this year?).</div>
<div><br></div>
<div><br></div>
<div>HTH,</div>
<div>David</div>
<div>
<div><br></div>
<div><br></div>
<blockquote style="border-left:#ccc 1px solid;margin:0px 0px 0px 0.8ex;padding-left:1ex" class="gmail_quote"><br>As a workaround, I would have liked to have been
able to use<br>ctest_build() to build both targets at once, but from
the<br>documentation it seems this is not possible, and I can't make a
CMake<br>target which depends on both "doc" and "all" either. The
only option<br>I can see then is to have CMakeLists.txt optionally make
"all" depend<br>on "doc" (I don't want to do this all the time, so would
need to pass<br>this in as an option via ctest_configure()). Any
other suggestions<br>are welcome!<br></blockquote></div></div></blockquote>
<div><br></div>
<div><br></div>
<div>Another suggestion worth considering: build your documentation as a test,
and control whether it is run by whatever means suit you best: a cmake option
to control a conditional add_test, or the "INCLUDE" or "EXCLUDE" option of
ctest_test to match by name at run time.</div>
<div><br></div>
<div><br></div>
<blockquote style="border-left:#ccc 1px solid;margin:0px 0px 0px 0.8ex;padding-left:1ex" class="gmail_quote">
<div class="gmail_quote">
<div>
<blockquote style="border-left:#ccc 1px solid;margin:0px 0px 0px 0.8ex;padding-left:1ex" class="gmail_quote"><br>Thanks in
advance,<br>David<br><br><br>----------------------------------------------<br>David
O'Shea<br>Senior Engineer<br>EMS SATCOM Pacific Pty Ltd.<br><br><a href="mailto:OShea.D@emsglobaltracking.com" target="_blank">OShea.D@emsglobaltracking.com</a><br><a href="http://www.emsglobaltracking.com" target="_blank">www.emsglobaltracking.com</a><br>
T: +61 8 8260
8187<br>_______________________________________________<br>Cdash mailing
list<br><a href="mailto:Cdash@public.kitware.com" target="_blank">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>
</blockquote></div></div><br></blockquote></div><br></div></div></blockquote></div>
</blockquote></div><br></div>