Works fine for me - so don't know whats different in your env - that is triggerig this.
Satish ------- [balay@pj01 petsc]$ make test globsearch="dm_impls_plex_tests-ex35_tet" TIMEOUT=5000 Using MAKEFLAGS: -- TIMEOUT=5000 globsearch=dm_impls_plex_tests-ex35_tet CC arch-linux-c-debug/tests/dm/impls/plex/tests/ex35.o CLINKER arch-linux-c-debug/tests/dm/impls/plex/tests/ex35 TEST arch-linux-c-debug/tests/counts/dm_impls_plex_tests-ex35_tet.counts ok dm_impls_plex_tests-ex35_tet ok diff-dm_impls_plex_tests-ex35_tet # ------------- # Summary # ------------- # success 2/2 tests (100.0%) # failed 0/2 tests (0.0%) # todo 0/2 tests (0.0%) # skip 0/2 tests (0.0%) # # Wall clock time for tests: 0 sec # Approximate CPU time (not incl. build time): 0.05 sec # # Timing summary (actual test time / total CPU time): # dm_impls_plex_tests-ex35_tet: 0.05 sec / 0.05 sec [balay@pj01 petsc]$ grep PETSC_HAVE_VALGRIND arch-linux-c-debug/include/petscconf.h [balay@pj01 petsc]$ On Mon, 16 Nov 2020, Matthew Knepley wrote: > WIth the latest master I get > > knepley/feature-tetgen-labels $:/PETSc3/petsc/petsc-pylith$ > PETSC_ARCH=arch-master-debug make -f ./gmakefile test > globsearch="dm_impls_plex_tests-ex35_tet" TIMEOUT=5000 EXTRA_O > PTIONS="" > Using MAKEFLAGS: EXTRA_OPTIONS= TIMEOUT=5000 > globsearch=dm_impls_plex_tests-ex35_tet > TEST > arch-master-debug/tests/counts/dm_impls_plex_tests-ex35_tet.counts > ok dm_impls_plex_tests-ex35_tet # SKIP Null requirement not met: > define(PETSC_HAVE_VALGRIND), Null requirement not met: > define(PETSC_HAVE_VALGRIND) > > I cannot trace it through yet. I reconfigured and rebuilt, and I still get > this. Does anyone know what is happening? > > Is it connected to the latest valgrind thing? > > Thanks, > > Matt > >