==2643334== Memcheck, a memory error detector ==2643334== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==2643334== Using Valgrind-3.18.1 and LibVEX; rerun with -h for copyright info ==2643334== Command: /home/github/actions-runner/_work/Chaste/Chaste/Chaste/chaste-build-dir/lung/test/TestImpedancePostProcessor -malloc_debug -malloc_dump -memory_info ==2643334== Parent PID: 2622576 ==2643334== ==2643334== WARNING: pwritev(vector[...]) is an obsolete suppression line not supported in valgrind 3.15 or later. ==2643334== You should replace [...] by a specific index such as [0] or [1] or [2] or similar ==2643334== ==2643334== ==2643334== FILE DESCRIPTORS: 7 open (3 std) at exit. ==2643334== Open file descriptor 117: ==2643334== ==2643334== ==2643334== Open file descriptor 110: ==2643334== ==2643334== ==2643334== Open file descriptor 4: /home/github/actions-runner/_work/Chaste/Chaste/Chaste/chaste-build-dir/memtest/TestImpedancePostProcessor_valgrind.txt ==2643334== ==2643334== ==2643334== Open file descriptor 3: /home/github/actions-runner/_work/Chaste/Chaste/Chaste/chaste-build-dir/Testing/Temporary/LastTest.log.tmp ==2643334== ==2643334== ==2643334== ==2643334== HEAP SUMMARY: ==2643334== in use at exit: 24 bytes in 2 blocks ==2643334== total heap usage: 5,600 allocs, 5,598 frees, 602,814 bytes allocated ==2643334== ==2643334== LEAK SUMMARY: ==2643334== definitely lost: 0 bytes in 0 blocks ==2643334== indirectly lost: 0 bytes in 0 blocks ==2643334== possibly lost: 0 bytes in 0 blocks ==2643334== still reachable: 24 bytes in 2 blocks ==2643334== suppressed: 0 bytes in 0 blocks ==2643334== Reachable blocks (those to which a pointer was found) are not shown. ==2643334== To see them, rerun with: --leak-check=full --show-leak-kinds=all ==2643334== ==2643334== For lists of detected and suppressed errors, rerun with: -s ==2643334== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)