It's doing the right thing:
From src/dm/impls/plex/tests/ex35.c:
build:
requires: !define(PETSC_USE_64BIT_INDICES) double !complex
!define(PETSC_HAVE_VALGRIND)
So because you have it defined PETSC_HAVE_VALGRIND, it's instructed to
skip the build and thus
you have:
# SKIP Null requirement not met:
The language is confusing because it's like a double negative, but it's
reporting the right thing.
Scott
On 11/16/20 10:37 AM, Matthew Knepley wrote:
On Mon, Nov 16, 2020 at 11:36 AM Satish Balay <[email protected]
<mailto:[email protected]>> wrote:
Works fine for me - so don't know whats different in your env -
that is triggerig this.
I had PETSC_HAVE_VALGRIND defined. When I remove it, everything works
fine. Why is that killing the test system?
Thanks,
Matt
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
>
>
--
What most experimenters take for granted before they begin their
experiments is infinitely more interesting than any results to which
their experiments lead.
-- Norbert Wiener
https://www.cse.buffalo.edu/~knepley/
<http://www.cse.buffalo.edu/%7Eknepley/>
--
Tech-X Corporation [email protected]
5621 Arapahoe Ave, Suite A Phone: (720) 974-1841
Boulder, CO 80303 Fax: (303) 448-7756
