Strange this never bit before, you could put in requires: for this example no gcov
> On Jun 14, 2023, at 2:37 PM, Satish Balay via petsc-dev > <petsc-dev@mcs.anl.gov> wrote: > > not ok vec_pf_impls_string_tests-ex1_1 # Error code: 65 > # [0]PETSC ERROR: --------------------- Error Message > -------------------------------------------------------------- > # [0]PETSC ERROR: Unable to open file > # [0]PETSC ERROR: Unable to open dynamic library: > # /tmp/svcpetsc/libpetscdlib.so > > which part of code is creating and loading a library from this location? > > > src/vec/pf/impls/string/cstring.c: PetscCall(PetscSNPrintf(task, > PETSC_STATIC_ARRAY_LENGTH(task), "cd %s ; if [ ! -d ${USERNAME} ]; then mkdir > ${USERNAME}; fi ; cd ${USERNAME} ; rm -f makefile petscdlib.* ; cp -f > ${PETSC_DIR}/src/vec/pf/impls/string/makefile ./makefile ; ${PETSC_MAKE} > NIN=%" PetscInt_FMT " NOUT=%" PetscInt_FMT " -f makefile libpetscdlib > STRINGFUNCTION=\"%s\" %s ; sync\n", tmp, pf->dimin, pf->dimout, string, > keeptmpfiles ? "; rm -f makefile petscdlib.c" : "")); > > > a library should be doing such a thing - in a common location [however useful > such a feature is :(] > > Satish > > On Wed, 14 Jun 2023, Matthew Knepley wrote: > >> https://gitlab.com/petsc/petsc/-/jobs/4474550390 >> >> It looks like some gcov stuff is failing in the CI, unrelated to this MR. >> >> Thanks, >> >> Matt >> >> >