Hi David, <br><br>It fixed it. <br><br>You guys are awesome.<br>Thank you very much,<br><br clear="all">Michele<br><br><div class="gmail_quote">On Wed, May 9, 2012 at 10:15 AM, David Cole <span dir="ltr"><<a href="mailto:david.cole@kitware.com" target="_blank">david.cole@kitware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">In addition to the article you read, you also need to read the<br>
addendum found here:<br>
<br>
<a href="http://www.kitware.com/blog/home/post/11" target="_blank">http://www.kitware.com/blog/home/post/11</a><br>
<br>
Basically, you need to add "APPEND" to your ctest_build command when<br>
submitting by parts. If you don't, then the CDash server will erase<br>
any previous submissions as it processes the Build.xml file...<br>
<br>
Give that a try, and let us know if you still have any more questions.<br>
<br>
<br>
HTH,<br>
David<br>
<div><div class="h5"><br>
<br>
On Wed, May 9, 2012 at 12:45 AM, Michele Caramello<br>
<<a href="mailto:mcaramello@invensense.com">mcaramello@invensense.com</a>> wrote:<br>
> I apologise if this is not the right list (I was undecided between this and<br>
> ctest AT <a href="http://cmake.org" target="_blank">cmake.org</a>).<br>
><br>
> I learned about the ctest(PARTS addition to cmake 2.7.2x when I read this<br>
> article <a href="http://www.kitware.com/products/html/CDashSubprojects.html" target="_blank">http://www.kitware.com/products/html/CDashSubprojects.html</a> and I<br>
> found it an useful and interesting feature.<br>
> I decided to put it to use although my projects are so small that the<br>
> benefits of a staggered submission is negligible compare to the legacy bulk<br>
> submission with the plain old ctest_submit() command.<br>
><br>
> I updated my Nightly ctest script to perform a ctest_submit of the<br>
> corresponding step that was just completed. The work flow is standard<br>
> (Update, Configure, Build) and my submission sequence was: Notes, Update,<br>
> Configure, Build.<br>
><br>
> When I looked at CDash, I found that the Build was the only step correctly<br>
> visualized and no trace of Note, Update, or Configure.<br>
> As puzzling as it was, I tried a few times, modified a few things, and<br>
> eventually ended up using ctest_submit(PARTS Notes Update Configure Build)<br>
> which worked, instead of the single steps submissions.<br>
> When analysing the output of ctest with -VV, I noticed that the Build.xml<br>
> file was submitted first, no matter what the ordering of the parameters for<br>
> the PARTS parameter was: that didn't tell me much, initially.<br>
><br>
> Moving on, I tried breaking down the ctest_submit back into the single steps<br>
> pieces to experiment a little. I eventually came to the conclusion that the<br>
> Build step must be submitted first in order for the others to appear<br>
> correctly on the dashboard.<br>
><br>
> Having access to the actual CDash mysql database, I queried the entries by<br>
> submitting the steps one by one manually. It seems to me (although I must<br>
> admit neither I looked at the php code too well nor I am an expert,<br>
> therefore I might be completely out of track) that the entries in the<br>
> index.php?project=PROJECT_NAME page all refer back to the build IDs from the<br>
> build table of the database. I found the 2 build2update and build2note<br>
> tables to be the only way one can correlate a build ID to an update ID and a<br>
> note, respectively, while the configure table stores the buildid<br>
> information.<br>
><br>
> I am wondering if this speaks of CDash needing a build ID available (and<br>
> therefore an entry in the build table as provided by the Build step) prior<br>
> to submitting Notes, Update, and/or Configure steps to be able to<br>
> cross-correlate the info correctly?<br>
> If so, could there be a workaround consisting of perhaps submitting an stub<br>
> Build step first to allow any ordering of the submit steps (the actual Build<br>
> step would come later in the game and perhaps overwrite the previous Build<br>
> info used as stub? Would that even be possible?<br>
><br>
> I am looking forward to hearing your thoughts.<br>
> Thanks you and Regards,<br>
><br>
> Michele Caramello<br>
> Software Testing Engineering Manager,<br>
> MotionProcessing Business Unit<br>
> InvenSense, Inc.<br>
> (O) 408 - 988 - 7339 x126<br>
> Email: <a href="mailto:mcaramello@invensense.com">mcaramello@invensense.com</a><br>
><br>
</div></div>> _______________________________________________<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>
><br>
</blockquote></div><br>