Re: [CMake] Viewing the full build log from the CDash Dashboard

2014-08-15 Thread David Cole via CMake
 Apologies if this is a stupid question with an obvious answer staring
 me in the face but...

Nope, it's not.

The dashboard does not have the full build log because ctest does not
send the full output from the build step. Only the contents of
Build.xml are sent when a build is submitted to CDash. The reason is
simply volume and scale. The configure output is typically fairly
small (so we send all of it), but build output can be megabytes and
megabytes (so we only send what we think is important...).

So CDash shows its cut-down summary because that's all it has.

To get the full build output, you need access to the machine that
submitted the dashboard. The full build log is found in the build tree
in a file named Testing/Temporary/LastBuild_20140806-1658.log (but
adjust the timestamp part of the name to when the build actually
occurred.)


 Our current build system captures the output of the ctest process and
 emails it separately but surely this must be available through CDash?

Nope. If you need it, keep your current system for now.


HTH,
David C.


-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake


Re: [CMake] Viewing the full build log from the CDash Dashboard

2014-08-15 Thread Nils Gladitz

On 15.08.2014 01:59, matt.bol...@csiro.au wrote:
CDash will show a cut-down summary of where it thinks the errors or 
warnings are but sometimes (especially with parallel builds) these are 
wrong (or false positives) or alternatively everything succeeded but 
you still want to browse through the build output.


In case you are using one of the makefile or ninja generators CTest 
launchers might help a bit[1].


Every compile, link and custom command will be wrapped by a command that 
captures the output and command line of its child process.
You still don't get the output of successful commands on your Dashboard 
but full output (not sure if there is a limit) of failed commands.


A random CMake dashboard submission with launchers looks e.g. like this:
http://open.cdash.org/viewBuildError.php?type=1buildid=3450912

Nils

[1] 
http://www.cmake.org/cmake/help/v3.0/module/CTest.html?highlight=ctest_use_launchers


-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

[CMake] Viewing the full build log from the CDash Dashboard

2014-08-14 Thread Matt.Bolger
Apologies if this is a stupid question with an obvious answer staring me in the 
face but...

How does one view the full build log from the dashboard? This relates to our 
own dashboard but looking at a build of CMake as an example  
(http://open.cdash.org/buildSummary.php?buildid=3450103) The full output of the 
configure step seems to be displayed on the buildSummary page but there's 
nothing for the actual build (gmake in this case) step. CDash will show a 
cut-down summary of where it thinks the errors or warnings are but sometimes 
(especially with parallel builds) these are wrong (or false positives) or 
alternatively everything succeeded but you still want to browse through the 
build output.

Our current build system captures the output of the ctest process and emails it 
separately but surely this must be available through CDash?

Thanks
Matt
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake