[CMake] Strange 2.8.4 memcheck result on CDash

[Kelly Thompson]

Allen,

 

We experienced something similar.  Unfortunately, I never diagnosed the
actual problem because I assumed that my ctest scripts were simply
out-of-date and I replaced them.  In particular, the ctest scripts that
produced broken memcheck output were trying to use the 'ctest
-DNightlyMemCheck' dashboard mode.  In my case, the log files had all of the
valgrind information, but the xml files were missing the valgrind output.

 

I replaced my ctest scripts with ones downloaded from the CTest Template
Script from our Dashboard's Client tab.  These new scripts use the
ctest_start(), ctest_configure(), ., ctest_memcheck(), etc. commands.  This
change (and possibly some new variables being set) appears to have fixed our
issues with valgrind output not showing up in the dashboard.

 

-kt

 

From: cmake-bounces at cmake.org [mailto:cmake-bounces at cmake.org] On Behalf Of
Allen D Byrne
Sent: Tuesday, February 22, 2011 7:48 AM
To: cmake at cmake.org
Subject: [CMake] Strange 2.8.4 memcheck result on CDash

 

The question is: Has anyone experienced problems with Dynamic Analysis
reports on CDash with the new cmake 2.8.4?

Our execution seemed to have produced the correct logs, yet on CDash the
report is 0 (ZERO). Looking at the output of the test it just shows one long
line of characters (no words) which seem like an encoded message? The only
change was a switch from 2.8.2 to 2.8.4. BTW, this was from a linux machine
using Valgrind.

Allen

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.cmake.org/pipermail/cmake/attachments/20110222/388dec74/attachment.htm>