Re: [CMake] Strange 2.8.4 memcheck result on CDash
David, Results so far: MemCheck with 2.8.4 - CDash does not display DynamicAnalysis data MemoryCheck with 2.8.3 displayed same issue The DynamicAnalysis_xxx.log files have the data. The DynamicAnalysis_xxx.xml files have the test data, but the Log tags data looks encyrpted. We will rerun with 2.8.2 and rerun 2.8.4 with MemoryCheck. Also we will cut back to just the base library tests. I will report back with results, Allen It looks to me from: git gui blame -- Source/cmCTest.cxx that this is the behavior that has always been -- ever since the -D MemCheck -D MemoryCheck stuff has been added to ctest several years ago. Are you sure that nothing else changed (besides CMake from 2.8.2 to 2.8.4 in this scenario)? Are we sure that executing ctest -D NightlyMemCheck with ctest 2.8.2 was doing what you thought it was doing? Let me know what you find out after your results are in... Thanks, David ___ 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
Re: [CMake] Strange 2.8.4 memcheck result on CDash
Further results: 2.8.2 works with MemoryCheck 2.8.4 does not display even with MemoryCheck. Here is out CTestConfig.cmake file: # SET (CTEST_PROJECT_NAME HDF5.1.8) SET (CTEST_NIGHTLY_START_TIME 20:00:00 CST) SET (CTEST_DROP_METHOD http) SET (CTEST_DROP_SITE nei.hdfgroup.uiuc.edu) SET (CTEST_DROP_LOCATION /cdash/submit.php?project=HDF5.1.8) SET (CTEST_DROP_SITE_CDASH TRUE) SET (UPDATE_TYPE svn) SET (VALGRIND_COMMAND /usr/bin/valgrind) SET (VALGRIND_COMMAND_OPTIONS -v --tool=memcheck --leak-check=full --track-fds=yes --num-callers=50 --show-reachable=yes --track-origins=yes --malloc-fill=0xff --free-fill=0xfe) SET (MEMORYCHECK_COMMAND /usr/bin/valgrind) SET (MEMORYCHECKCOMMAND /usr/bin/valgrind) SET (CTEST_MEMORYCHECK_COMMAND_OPTIONS -v --tool=memcheck --leak-check=full --track-fds=yes --num-callers=50 --show-reachable=yes --track-origins=yes --malloc-fill=0xff --free-fill=0xfe) SET (CTEST_MEMORYCHECKCOMMAND_OPTIONS -v --tool=memcheck --leak-check=full --track-fds=yes --num-callers=50 --show-reachable=yes --track-origins=yes --malloc-fill=0xff --free-fill=0xfe) SET (CTEST_TESTING_TIMEOUT 3600) SET (DART_TESTING_TIMEOUT 3600) # Allen It looks to me from: git gui blame -- Source/cmCTest.cxx that this is the behavior that has always been -- ever since the -D MemCheck -D MemoryCheck stuff has been added to ctest several years ago. Are you sure that nothing else changed (besides CMake from 2.8.2 to 2.8.4 in this scenario)? Are we sure that executing ctest -D NightlyMemCheck with ctest 2.8.2 was doing what you thought it was doing? Let me know what you find out after your results are in... Thanks, David ___ 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
Re: [CMake] Strange 2.8.4 memcheck result on CDash
Can you send me (offlist) copies of the DynamicAnalysis.xml files from each case? Do you still have them? If not, no worried. I'll try to reproduce this on our CMake dashboard by submitting a 2nd valgrind dashboard: same script, just drive it with 2.8.4. It may take me a few days to get around to this, but I'll keep you posted. Thanks, David On Wed, Feb 23, 2011 at 4:31 PM, Allen D Byrne b...@hdfgroup.org wrote: Further results: 2.8.2 works with MemoryCheck 2.8.4 does not display even with MemoryCheck. Here is out CTestConfig.cmake file: # SET (CTEST_PROJECT_NAME HDF5.1.8) SET (CTEST_NIGHTLY_START_TIME 20:00:00 CST) SET (CTEST_DROP_METHOD http) SET (CTEST_DROP_SITE nei.hdfgroup.uiuc.edu) SET (CTEST_DROP_LOCATION /cdash/submit.php?project=HDF5.1.8) SET (CTEST_DROP_SITE_CDASH TRUE) SET (UPDATE_TYPE svn) SET (VALGRIND_COMMAND /usr/bin/valgrind) SET (VALGRIND_COMMAND_OPTIONS -v --tool=memcheck --leak-check=full --track-fds=yes --num-callers=50 --show-reachable=yes --track-origins=yes --malloc-fill=0xff --free-fill=0xfe) SET (MEMORYCHECK_COMMAND /usr/bin/valgrind) SET (MEMORYCHECKCOMMAND /usr/bin/valgrind) SET (CTEST_MEMORYCHECK_COMMAND_OPTIONS -v --tool=memcheck --leak-check=full --track-fds=yes --num-callers=50 --show-reachable=yes --track-origins=yes --malloc-fill=0xff --free-fill=0xfe) SET (CTEST_MEMORYCHECKCOMMAND_OPTIONS -v --tool=memcheck --leak-check=full --track-fds=yes --num-callers=50 --show-reachable=yes --track-origins=yes --malloc-fill=0xff --free-fill=0xfe) SET (CTEST_TESTING_TIMEOUT 3600) SET (DART_TESTING_TIMEOUT 3600) # Allen It looks to me from: git gui blame -- Source/cmCTest.cxx that this is the behavior that has always been -- ever since the -D MemCheck -D MemoryCheck stuff has been added to ctest several years ago. Are you sure that nothing else changed (besides CMake from 2.8.2 to 2.8.4 in this scenario)? Are we sure that executing ctest -D NightlyMemCheck with ctest 2.8.2 was doing what you thought it was doing? Let me know what you find out after your results are in... Thanks, David ___ 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
Re: [CMake] Strange 2.8.4 memcheck result on CDash
Here is a snippet of first the 2.8.2 xml file followed by the 2.8.4 file: # Test Status=failed Nametesthdf5/Name Path./test/Path FullName./test/testhdf5/FullName FullCommandLine/usr/bin/valgrind -v --tool=memcheck --leak-check=full --track-fds=yes --num-callers=50 --show-reachable=yes --track-origins=yes --malloc-fill=0xff --free-fill=0xfe /home/hdftest/snapshots-cmake-hdf5_1_8/TestDir/jam/bin/testhdf5/FullCommandLine Results /Results Log ==25013== Memcheck, a memory error detector ==25013== Copyright (C) 2002-2009, and GNU GPLapos;d, by Julian Seward et al. ==25013== Using Valgrind-3.5.0 and LibVEX; rerun with -h for copyright info ==25013== Command: /home/hdftest/snapshots-cmake-hdf5_1_8/TestDir/jam/bin/testhdf5 ==25013== ==25013== WARNING: new redirection conflicts with existing -- ignoring it --25013-- Valgrind options: --25013---v --25013----tool=memcheck --25013----leak-check=full --25013----track-fds=yes --25013----num-callers=50 --25013----show-reachable=yes --25013----track-origins=yes --25013----malloc-fill=0xff --25013----free-fill=0xfe --25013-- Contents of /proc/version: --25013-- Linux version 2.6.18-194.3.1.el5PAE (mockbu...@builder10.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-48)) #1 SMP Thu May 13 13:48:44 EDT 2010 --25013-- Arch and hwcaps: X86, x86-sse1-sse2 # Test Status=failed Nametesthdf5/Name Path./test/Path FullName./test/testhdf5/FullName FullCommandLine/usr/bin/valgrind quot;-vquot; quot;--tool=memcheckquot; quot;--leak-check=fullquot; quot;--track-fds=yesquot; quot;--num-callers=50quot; quot;--show-reachable=yesquot; quot;--track-origins=yesquot; quot;--malloc-fill=0xffquot; quot;--free-fill=0xfequot; quot;/home/hdftest/snapshots-cmake-hdf5/TestDir/jam/bin/testhdf5quot;/FullCommandLine Results /Results Log eJylV9tu2zgQfc9XDLAPtYHKkm3ZlrPwYoPc2kXSBnHa7VtAUSOLjSQaJOXE/fod0ndHalOs0ToyeeZwOHdNJt1xfzyeTOAWC54hf3oPDAospFoCKiUVJGiQG6lOJlvsuZwvlZhlBlrnbegFQc+jrzGJlglcf/oC13c375L3EC/hnyoXrIQpPjOVABpgeWeP6YsW5Qy+snymRJl4/c6gEziWGxF/vfz2JyhUVQnPwmTgZZCSPnx7uChTeaBVUZDoKfiZLNDPktSgNr4u2Vxn0miPF+wJPVof+A+0cyGU/50VfixK3yLtxh7diee5R8/b6gdyboQs9eneHn28xdFvz0iZT4q1RY83c2RPntuZpFWev5JVjD95aaInS9THm2VVeJzlOSo9GQTHu3TNZ08h4xmLc6yTX5FLsp8oaw8oiFxyLxV5Pgle0vR4P1WI213c2z2XpcHSaJAp+HMlub8gJclah8a6EWX1Aust6HWGnW5E22Gn3+l2MB/cnV1Cq5D8Ka5EnvztvlF1gw4ncqk7Us3a0JpxvuUISbBngzAKRkEIrXtM4AMzq3UvjNpt+KML09s7eMgquGVL6Pbp32kYnYYhXF48kGx335RnimcuBrNnTqFzCt+i4Xt4iYae1ti1X7099B2bIWjxAwnIK6VIzXwJYTAmmYK9gK7mc6kMKWXX6oIqF7FilG6JUC7RlhTBlVY+rfuLNWhP7h5ZYpNGLwsNqZIFOGSeeD3KHi2hFbx0GQ+CoP1zqaKk5OCq608pQx5+O1XsOVEQRr8+6Pgy/iYzPGvU3EUEkfUt1REbfWT8ncwCiURdvjOQsQVSiUqWJSsEt8fEMgdjA75OC7K+Qm0DhbQROdbY1k8wZVVuOha8z3F58fH+FMiavDvqB9AiLL60qSStPEUuNRKc3n0Moz60FrO7nInyka716K716Dgerz7fP66Ef9NQixlpn0uWPHKpcGeutZvDgCL3982/Y33tiB1z3zHv6uG/Z/efPn66PoUSn7c2sAnIZZnmglPquzKNL0IbqwJpI2Yl1Rp6FubQqZbEmpYusG9cOPy04d77y6JIneEwDMCBGlwUJcSijcqxfO0jSxD1doA35JOIi72M6veGb7c0/f9BcrYAdfpOetR/a2D/KqAP85cS0Z9TSacipH39Q8x9nTG6vI8ll1Q4fVdvqcx6VDI3ummnXK8TUK91vu6+oVqsZfl+leHxsdzGH71+PGTErhpyxvpjMNgB6jn4gHzeoiDVaOo54mgHqOcYspQg3LW1Wo4wjnALaLgLee8XsRXUx9aeHmijvGjWYxCNcAuo52DYXR3D58tajlES7AD1HKOe8wv+RJFxL9kh6lnC8ZhY7DBQTxGOo/V2w00Stla0mDdYNNkBGqKjiwSJGxkY22w3yLP+KngarclGO0BDZAzSlZplI0mMe4gGTcJkdVAhF/UGHTqWDaJBl3CrS6NRh3uIppxjq5PmjTfqJXuIk5MrGsozzOdQafxfwzdN+ERzQiXriY5zzcQtbya9bmdM+tD4rBGi4MTS2CIFq+kzFbNKIb2upKIUbkynrHbLbTjAXtrSSD+o768e6H3HUEAaZm+1ejoSObdNUlcFvb3MqKGZrCDu9doR9AFVaae5KTI7Rz5QDpAiRpsj3O3qHesDkoGgldGfNjR4JFhXQZ6pereO0x2gniPp2fhR7PlnNHx8gDlQd/ok5jS8a+ryLU3PuXh1o3tMkcZfjuSNqrTMU2Obv7bFJKWoO8Lf0MvKDS4whysazOCj/5lKBj012sHNCdo0B6brKGtAQ91h0bqssPqOMgqCHeBA3WssUdHE+XnVtq+qkq+jbNXI9dH1LiiMNPVm6/5s0LhL45NUFIXMoAtY+nGMnbqWvjmYIoYaO8WP1rbrk7IyOw7CM0OWjytHycwry08piTbKa/dMgP8AyATV4g== # Allen Can you send me (offlist) copies of the DynamicAnalysis.xml files from each case? Do you still have them? If not, no worried. I'll try to reproduce this on our CMake dashboard by submitting a 2nd valgrind dashboard: same script, just drive it with 2.8.4. It may take me a few days to get around to this, but I'll keep you posted. Thanks, David On Wed, Feb 23, 2011 at 4:31 PM, Allen D Byrne b...@hdfgroup.org wrote: Further results: 2.8.2 works with MemoryCheck 2.8.4 does not display even with MemoryCheck. Here is out CTestConfig.cmake file: # SET (CTEST_PROJECT_NAME HDF5.1.8) SET (CTEST_NIGHTLY_START_TIME 20:00:00 CST) SET (CTEST_DROP_METHOD http) SET (CTEST_DROP_SITE nei.hdfgroup.uiuc.edu) SET (CTEST_DROP_LOCATION /cdash/submit.php?project=HDF5.1.8) SET
Re: [CMake] Strange 2.8.4 memcheck result on CDash
What version of CDash is your server running? I'm trying to view it in my web browser to find out for myself, but when I try ( http://nei.hdfgroup.uiuc.edu/cdash ), I get a Problem loading page message from Firefox. I suspect we're compressing the test results, but CDash is not de-compressing them. On Wed, Feb 23, 2011 at 4:55 PM, Allen D Byrne b...@hdfgroup.org wrote: Here is a snippet of first the 2.8.2 xml file followed by the 2.8.4 file: # Test Status=failed Nametesthdf5/Name Path./test/Path FullName./test/testhdf5/FullName FullCommandLine/usr/bin/valgrind -v --tool=memcheck --leak-check=full --track-fds=yes --num-callers=50 --show-reachable=yes --track-origins=yes --malloc-fill=0xff --free-fill=0xfe /home/hdftest/snapshots-cmake-hdf5_1_8/TestDir/jam/bin/testhdf5/FullCommandLine Results /Results Log ==25013== Memcheck, a memory error detector ==25013== Copyright (C) 2002-2009, and GNU GPLapos;d, by Julian Seward et al. ==25013== Using Valgrind-3.5.0 and LibVEX; rerun with -h for copyright info ==25013== Command: /home/hdftest/snapshots-cmake-hdf5_1_8/TestDir/jam/bin/testhdf5 ==25013== ==25013== WARNING: new redirection conflicts with existing -- ignoring it --25013-- Valgrind options: --25013-- -v --25013-- --tool=memcheck --25013-- --leak-check=full --25013-- --track-fds=yes --25013-- --num-callers=50 --25013-- --show-reachable=yes --25013-- --track-origins=yes --25013-- --malloc-fill=0xff --25013-- --free-fill=0xfe --25013-- Contents of /proc/version: --25013-- Linux version 2.6.18-194.3.1.el5PAE (mockbu...@builder10.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-48)) #1 SMP Thu May 13 13:48:44 EDT 2010 --25013-- Arch and hwcaps: X86, x86-sse1-sse2 # Test Status=failed Nametesthdf5/Name Path./test/Path FullName./test/testhdf5/FullName FullCommandLine/usr/bin/valgrind quot;-vquot; quot;--tool=memcheckquot; quot;--leak-check=fullquot; quot;--track-fds=yesquot; quot;--num-callers=50quot; quot;--show-reachable=yesquot; quot;--track-origins=yesquot; quot;--malloc-fill=0xffquot; quot;--free-fill=0xfequot; quot;/home/hdftest/snapshots-cmake-hdf5/TestDir/jam/bin/testhdf5quot;/FullCommandLine Results /Results Log eJylV9tu2zgQfc9XDLAPtYHKkm3ZlrPwYoPc2kXSBnHa7VtAUSOLjSQaJOXE/fod0ndHalOs0ToyeeZwOHdNJt1xfzyeTOAWC54hf3oPDAospFoCKiUVJGiQG6lOJlvsuZwvlZhlBlrnbegFQc+jrzGJlglcf/oC13c375L3EC/hnyoXrIQpPjOVABpgeWeP6YsW5Qy+snymRJl4/c6gEziWGxF/vfz2JyhUVQnPwmTgZZCSPnx7uChTeaBVUZDoKfiZLNDPktSgNr4u2Vxn0miPF+wJPVof+A+0cyGU/50VfixK3yLtxh7diee5R8/b6gdyboQs9eneHn28xdFvz0iZT4q1RY83c2RPntuZpFWev5JVjD95aaInS9THm2VVeJzlOSo9GQTHu3TNZ08h4xmLc6yTX5FLsp8oaw8oiFxyLxV5Pgle0vR4P1WI213c2z2XpcHSaJAp+HMlub8gJclah8a6EWX1Aust6HWGnW5E22Gn3+l2MB/cnV1Cq5D8Ka5EnvztvlF1gw4ncqk7Us3a0JpxvuUISbBngzAKRkEIrXtM4AMzq3UvjNpt+KML09s7eMgquGVL6Pbp32kYnYYhXF48kGx335RnimcuBrNnTqFzCt+i4Xt4iYae1ti1X7099B2bIWjxAwnIK6VIzXwJYTAmmYK9gK7mc6kMKWXX6oIqF7FilG6JUC7RlhTBlVY+rfuLNWhP7h5ZYpNGLwsNqZIFOGSeeD3KHi2hFbx0GQ+CoP1zqaKk5OCq608pQx5+O1XsOVEQRr8+6Pgy/iYzPGvU3EUEkfUt1REbfWT8ncwCiURdvjOQsQVSiUqWJSsEt8fEMgdjA75OC7K+Qm0DhbQROdbY1k8wZVVuOha8z3F58fH+FMiavDvqB9AiLL60qSStPEUuNRKc3n0Moz60FrO7nInyka716K716Dgerz7fP66Ef9NQixlpn0uWPHKpcGeutZvDgCL3982/Y33tiB1z 3zHv6uG/Z/efPn66PoUSn7c2sAnIZZnmglPquzKNL0IbqwJpI2Yl1Rp6FubQqZbEmpYusG9cOPy04d77y6JIneEwDMCBGlwUJcSijcqxfO0jSxD1doA35JOIi72M6veGb7c0/f9BcrYAdfpOetR/a2D/KqAP85cS0Z9TSacipH39Q8x9nTG6vI8ll1Q4fVdvqcx6VDI3ummnXK8TUK91vu6+oVqsZfl+leHxsdzGH71+PGTErhpyxvpjMNgB6jn4gHzeoiDVaOo54mgHqOcYspQg3LW1Wo4wjnALaLgLee8XsRXUx9aeHmijvGjWYxCNcAuo52DYXR3D58tajlES7AD1HKOe8wv+RJFxL9kh6lnC8ZhY7DBQTxGOo/V2w00Stla0mDdYNNkBGqKjiwSJGxkY22w3yLP+KngarclGO0BDZAzSlZplI0mMe4gGTcJkdVAhF/UGHTqWDaJBl3CrS6NRh3uIppxjq5PmjTfqJXuIk5MrGsozzOdQafxfwzdN+ERzQiXriY5zzcQtbya9bmdM+tD4rBGi4MTS2CIFq+kzFbNKIb2upKIUbkynrHbLbTjAXtrSSD+o768e6H3HUEAaZm+1ejoSObdNUlcFvb3MqKGZrCDu9doR9AFVaae5KTI7Rz5QDpAiRpsj3O3qHesDkoGgldGfNjR4JFhXQZ6pereO0x2gniPp2fhR7PlnNHx8gDlQd/ok5jS8a+ryLU3PuXh1o3tMkcZfjuSNqrTMU2Obv7bFJKWoO8Lf0MvKDS4whysazOCj/5lKBj012sHNCdo0B6brKGtAQ91h0bqssPqOMgqCHeBA3WssUdHE+XnVtq+qkq+jbNXI9dH1LiiMNPVm6/5s0LhL45NUFIXMoAtY+nGMnbqWvjmYIoYaO8WP1rbrk7IyOw7CM0OWjytHycwry08piTbKa/dMgP8AyATV4g== # Allen Can you send me (offlist) copies of the DynamicAnalysis.xml files from each case? Do you still have them? If not, no worried. I'll try to reproduce this on our CMake dashboard by submitting a 2nd valgrind dashboard: same script, just drive it with 2.8.4. It may take me a few days to get around to this, but I'll keep you posted. Thanks, David On Wed, Feb 23, 2011 at 4:31 PM, Allen D Byrne b...@hdfgroup.org wrote: Further results: 2.8.2 works with MemoryCheck 2.8.4 does not display even with MemoryCheck. Here is out CTestConfig.cmake file: # SET (CTEST_PROJECT_NAME
Re: [CMake] Strange 2.8.4 memcheck result on CDash
On 2/22/2011 9:48 AM, Allen D Byrne wrote: 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 Is this a public dashboard? Can you send the .xml files to me off the list so I can have a look at them? Thanks. -Bill ___ 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
Re: [CMake] Strange 2.8.4 memcheck result on CDash
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-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of Allen D Byrne Sent: Tuesday, February 22, 2011 7:48 AM To: cmake@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 ___ 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
Re: [CMake] Strange 2.8.4 memcheck result on CDash
Allen, I'm not sure what, if anything, changed in the ctest code, but I have this observation to offer. Try: ctest -D NightlyMemoryCheck When I use NightlyMemoryCheck all of the dashboard steps execute, and the submit at the end includes the dynamic analysis xml file in the submission. When I use NightlyMemCheck, ONLY the memory checking step executes, producing the dynamic analysis xml file, but not doing any other build steps, and not submitting it. I will investigate when this changed and why, but for now, hopefully that can get you going without completely revamping your scripts. HTH, David On Tue, Feb 22, 2011 at 9:48 AM, Allen D Byrne b...@hdfgroup.org wrote: 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 ___ 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 ___ 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
Re: [CMake] Strange 2.8.4 memcheck result on CDash
David, We are currently testing 2.8.3 with the MemCheck and we will test 2.8.4 with MemoryCheck tonight. I will report tomorrow on the results. Allen Allen, I'm not sure what, if anything, changed in the ctest code, but I have this observation to offer. Try: ctest -D NightlyMemoryCheck When I use NightlyMemoryCheck all of the dashboard steps execute, and the submit at the end includes the dynamic analysis xml file in the submission. When I use NightlyMemCheck, ONLY the memory checking step executes, producing the dynamic analysis xml file, but not doing any other build steps, and not submitting it. I will investigate when this changed and why, but for now, hopefully that can get you going without completely revamping your scripts. HTH, David On Tue, Feb 22, 2011 at 9:48 AM, Allen D Byrne b...@hdfgroup.org wrote: 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 ___ 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 ___ 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
Re: [CMake] Strange 2.8.4 memcheck result on CDash
It looks to me from: git gui blame -- Source/cmCTest.cxx that this is the behavior that has always been -- ever since the -D MemCheck -D MemoryCheck stuff has been added to ctest several years ago. Are you sure that nothing else changed (besides CMake from 2.8.2 to 2.8.4 in this scenario)? Are we sure that executing ctest -D NightlyMemCheck with ctest 2.8.2 was doing what you thought it was doing? Let me know what you find out after your results are in... Thanks, David On Tue, Feb 22, 2011 at 12:40 PM, Allen D Byrne b...@hdfgroup.org wrote: David, We are currently testing 2.8.3 with the MemCheck and we will test 2.8.4 with MemoryCheck tonight. I will report tomorrow on the results. Allen Allen, I'm not sure what, if anything, changed in the ctest code, but I have this observation to offer. Try: ctest -D NightlyMemoryCheck When I use NightlyMemoryCheck all of the dashboard steps execute, and the submit at the end includes the dynamic analysis xml file in the submission. When I use NightlyMemCheck, ONLY the memory checking step executes, producing the dynamic analysis xml file, but not doing any other build steps, and not submitting it. I will investigate when this changed and why, but for now, hopefully that can get you going without completely revamping your scripts. HTH, David On Tue, Feb 22, 2011 at 9:48 AM, Allen D Byrne b...@hdfgroup.org wrote: 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 ___ 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 ___ 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
