custom_details

command_line: /usr/bin/valgrind "--log-file=/home/runner/work/nightly-builds/nightly-builds/build/Testing/Temporary/MemoryChecker.6.log" "-q" "--tool=memcheck" "--leak-check=yes" "--show-reachable=yes" "--num-callers=50" "/opt/hostedtoolcache/cmake/4.2.1/x64/cmake-4.2.1-linux-x86_64/bin/cmake" "-E" "echo" " test output <CTestDetails>CustomDetails</CTestDetails> more output "

working_directory: ""

Potential Memory Leak: 0

Processors: 1

DA Checker: Valgrind

Environment: #CTEST_RESOURCE_GROUP_COUNT=

Completion Status: CustomDetails

stdout:

    test output
    more output
    
==2814== 72,704 bytes in 1 blocks are still reachable in loss record 1 of 1
==2814==    at 0x4846828: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==2814==    by 0x42F345: ??? (in /opt/hostedtoolcache/cmake/4.2.1/x64/cmake-4.2.1-linux-x86_64/bin/cmake)
==2814==    by 0x118BA7C: ??? (in /opt/hostedtoolcache/cmake/4.2.1/x64/cmake-4.2.1-linux-x86_64/bin/cmake)
==2814==    by 0x4988263: __libc_start_main@@GLIBC_2.34 (libc-start.c:343)
==2814==    by 0x42F672: ??? (in /opt/hostedtoolcache/cmake/4.2.1/x64/cmake-4.2.1-linux-x86_64/bin/cmake)
==2814==    by 0x1FFEFFF5A7: ???
==2814==    by 0x37: ???
==2814==    by 0x3: ???
==2814==    by 0x1FFEFFFB16: ???
==2814==    by 0x1FFEFFFB5E: ???
==2814==    by 0x1FFEFFFB61: ???
==2814==    by 0x1FFEFFFB66: ???
==2814==

Example