<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">A service announcement, since I may have missed some memory leaks because of doing this wrong:<div class=""><br class=""></div><div class="">You can run the test suite with valgrind (as documented if you use `make -f gmakefile.test help-test`) with a command like</div><div class=""><br class=""></div><div class=""> VALGRIND=1 make -f gmakefile.test test globsearch="foo"</div><div class=""><br class=""></div><div class="">but any messages emitted by valgrind (which are directed to stderr) aren't directly visible. </div><div class=""><br class=""></div><div class="">The error messages appear in the $PETSC_ARCH/tests tree, in the subdirectories corresponding to the individual tests. One way to find any non-empty error files would be</div><div class=""><br class=""></div><div class=""> find $PETSC_ARCH/tests -name *.err ! -size 0 </div><div class=""><br class=""></div><div class="">I suspect there are other ways to accomplish this, so please share if you have a better workflow. In particular, I notice that in the nightly tests with valgrind, </div><div class="">a different method (lib/petsc/bin/mpiexec -valgrind ?) is being used.</div><div class="">e.g. <a href="http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2019/08/19/examples_master_arch-linux-pkgs-valgrind_es.log" class="">http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2019/08/19/examples_master_arch-linux-pkgs-valgrind_es.log</a></div></body></html>