June 2019 - petsc-checkbuilds - mailman3.cels.anl.gov

PETSc blame digest (next-tmp) 2019-06-28
by PETSc checkBuilds 28 Jun '19

28 Jun '19

Dear PETSc developer, This email contains listings of contributions attributed to you by `git blame` that caused compiler errors or warnings in PETSc automated testing. Follow the links to see the full log files. Please attempt to fix the issues promptly or let us know at petsc-dev(a)mcs.anl.gov if you are unable to resolve the issues. Thanks, The PETSc development team ---- warnings attributed to commit https://bitbucket.org/petsc/petsc/commits/d8d174d No more batch submission script; this is all due to a very smart idea of Lisandro Dalcin src/mat/impls/hypre/mhypre.c:630 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/28/build_next…] /Users/petsc/petsc.next-tmp-2/src/mat/impls/hypre/mhypre.c:630:10: error: use of undeclared identifier 'PetscObjectBASETypeCompare'; did you mean 'PetscObjectBaseTypeCompare'? [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/28/build_next…] /sandbox/petsc/petsc.next-tmp-3/src/mat/impls/hypre/mhypre.c:630:3: warning: implicit declaration of function 'PetscObjectBASETypeCompare' [-Wimplicit-function-declaration] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/28/build_next…] /home/sandbox/petsc/petsc.next-tmp/src/mat/impls/hypre/mhypre.c:630:3: warning: implicit declaration of function 'PetscObjectBASETypeCompare' [-Wimplicit-function-declaration] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/28/build_next…] /usr/home/balay/petsc.next-tmp-2/src/mat/impls/hypre/mhypre.c:630:10: error: 'PetscObjectBASETypeCompare' was not declared in this scope [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/28/build_next…] /sandbox/petsc/petsc.next-tmp-2/src/mat/impls/hypre/mhypre.c:630:10: error: use of undeclared identifier 'PetscObjectBASETypeCompare'; did you mean 'PetscObjectBaseTypeCompare'? [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/28/build_next…] /usr/home/balay/petsc.next-tmp-3/src/mat/impls/hypre/mhypre.c:630:10: warning: implicit declaration of function 'PetscObjectBASETypeCompare'; did you mean 'PetscObjectBaseTypeCompare'? [-Wimplicit-function-declaration] ---- To opt-out from receiving these messages - send a request to petsc-dev(a)mcs.anl.gov.

2 1

PETSc blame digest (next-tmp) 2019-06-27
by PETSc checkBuilds 27 Jun '19

27 Jun '19

Dear PETSc developer, This email contains listings of contributions attributed to you by `git blame` that caused compiler errors or warnings in PETSc automated testing. Follow the links to see the full log files. Please attempt to fix the issues promptly or let us know at petsc-dev(a)mcs.anl.gov if you are unable to resolve the issues. Thanks, The PETSc development team ---- warnings attributed to commit https://bitbucket.org/petsc/petsc/commits/63b8946 Add patterned SF graphs and use x as roots and y as leaves in x to y vecscatter src/vec/is/sf/interface/sf.c:433 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/27/build_next…] /sandbox/petsc/petsc.next-tmp-2/src/vec/is/sf/interface/sf.c:433:91: warning: variable 'comm' is uninitialized when used here [-Wuninitialized] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/27/build_next…] /Users/petsc/petsc.next-tmp-2/src/vec/is/sf/interface/sf.c:433:91: warning: variable 'comm' is uninitialized when used here [-Wuninitialized] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/27/build_next…] /Users/petsc/petsc.next-tmp-3/src/vec/is/sf/interface/sf.c:433:91: warning: variable 'comm' is uninitialized when used here [-Wuninitialized] ---- To opt-out from receiving these messages - send a request to petsc-dev(a)mcs.anl.gov.

2 1

PETSc blame digest (next-tmp) 2019-06-27
by PETSc checkBuilds 27 Jun '19

27 Jun '19

Dear PETSc developer, This email contains listings of contributions attributed to you by `git blame` that caused compiler errors or warnings in PETSc automated testing. Follow the links to see the full log files. Please attempt to fix the issues promptly or let us know at petsc-dev(a)mcs.anl.gov if you are unable to resolve the issues. Thanks, The PETSc development team ---- warnings attributed to commit https://bitbucket.org/petsc/petsc/commits/3af045c Fix Fortran SETERRQ() to new calling sequence when compiled with no error checking include/petscerror.h:143 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/27/build_next…] /home/petsc/petsc.next-tmp-3/include/petscerror.h:143:51: warning: 'comm' may be used uninitialized in this function [-Wmaybe-uninitialized] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/27/build_next…] /sandbox/petsc/petsc.next-tmp-3/include/petscerror.h:143:124: warning: 'comm' may be used uninitialized in this function [-Wmaybe-uninitialized] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/27/build_next…] /usr/home/balay/petsc.next-tmp-2/include/petscerror.h:143:51: warning: 'comm' may be used uninitialized in this function [-Wmaybe-uninitialized] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/27/build_next…] /usr/home/balay/petsc.next-tmp-3/include/petscerror.h:143:41: warning: 'comm' may be used uninitialized in this function [-Wmaybe-uninitialized] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/27/build_next…] /home/sandbox/petsc/petsc.next-tmp/include/petscerror.h:143:51: warning: 'comm' may be used uninitialized in this function [-Wmaybe-uninitialized] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/27/build_next…] /sandbox/petsc/petsc.next-tmp/include/petscerror.h:143:51: warning: 'comm' may be used uninitialized in this function [-Wmaybe-uninitialized] ---- To opt-out from receiving these messages - send a request to petsc-dev(a)mcs.anl.gov.

1 0

PETSc blame digest (next) 2019-06-24
by PETSc checkBuilds 24 Jun '19

24 Jun '19

Dear PETSc developer, This email contains listings of contributions attributed to you by `git blame` that caused compiler errors or warnings in PETSc automated testing. Follow the links to see the full log files. Please attempt to fix the issues promptly or let us know at petsc-dev(a)mcs.anl.gov if you are unable to resolve the issues. Thanks, The PETSc development team ---- warnings attributed to commit https://bitbucket.org/petsc/petsc/commits/5ef5176 DMPlexLoad_HDF5_Xdmf_Internal reads labels w/ DMPlexLoadLabels_HDF5_Internal. src/dm/impls/plex/plexhdf5.c:868 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /usr/home/balay/petsc.next-2/src/dm/impls/plex/plexhdf5.c:868:43: warning: left operand of comma operator has no effect [-Wunused-value] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /home/sandbox/petsc/petsc.next-3/src/dm/impls/plex/plexhdf5.c:868:80: warning: right operand of comma operator has no effect [-Wunused-value] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /usr/home/balay/petsc.next-2/src/dm/impls/plex/plexhdf5.c:868:103: warning: right operand of comma operator has no effect [-Wunused-value] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /sandbox/petsc/petsc.next-2/src/dm/impls/plex/plexhdf5.c:868:100: warning: left-hand operand of comma expression has no effect [-Wunused-value] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /home/sandbox/petsc/petsc.next-3/src/dm/impls/plex/plexhdf5.c:868:107: error: 'PetscStackCallHDF5' was not declared in this scope [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /sandbox/petsc/petsc.next-2/src/dm/impls/plex/plexhdf5.c:868:41: warning: left-hand operand of comma expression has no effect [-Wunused-value] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /usr/home/balay/petsc.next-2/src/dm/impls/plex/plexhdf5.c:868:75: warning: right operand of comma operator has no effect [-Wunused-value] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /Users/petsc/petsc.next-3/src/dm/impls/plex/plexhdf5.c:868:80: warning: expression result unused [-Wunused-value] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /sandbox/petsc/petsc.next-3/src/dm/impls/plex/plexhdf5.c:868:56: warning: left-hand operand of comma expression has no effect [-Wunused-value] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /usr/home/balay/petsc.next/src/dm/impls/plex/plexhdf5.c:868:43: warning: left operand of comma operator has no effect [-Wunused-value] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /sandbox/petsc/petsc.next-2/src/dm/impls/plex/plexhdf5.c:868:72: warning: left-hand operand of comma expression has no effect [-Wunused-value] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /home/sandbox/petsc/petsc.next-3/src/dm/impls/plex/plexhdf5.c:868:103: warning: right operand of comma operator is a reference, not call, to function 'ReadLabelHDF5_Static' [-Waddress] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /sandbox/petsc/petsc.next-2/src/dm/impls/plex/plexhdf5.c:868:72: warning: left-hand operand of comma expression has no effect [-Wunused-value] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /usr/home/balay/petsc.next/src/dm/impls/plex/plexhdf5.c:868:75: warning: right operand of comma operator has no effect [-Wunused-value] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /sandbox/petsc/petsc.next-2/src/dm/impls/plex/plexhdf5.c:868:56: warning: left-hand operand of comma expression has no effect [-Wunused-value] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /sandbox/petsc/petsc.next-2/src/dm/impls/plex/plexhdf5.c:868:56: warning: left-hand operand of comma expression has no effect [-Wunused-value] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /Users/petsc/petsc.next-3/src/dm/impls/plex/plexhdf5.c:868:3: error: use of undeclared identifier 'PetscStackCallHDF5' [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /sandbox/petsc/petsc.next-2/src/dm/impls/plex/plexhdf5.c:868:100: warning: left-hand operand of comma expression has no effect [-Wunused-value] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /usr/home/balay/petsc.next-2/src/dm/impls/plex/plexhdf5.c:868:58: warning: right operand of comma operator has no effect [-Wunused-value] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /usr/home/balay/petsc.next-2/src/dm/impls/plex/plexhdf5.c:868:3: error: 'PetscStackCallHDF5' was not declared in this scope [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /Users/petsc/petsc.next-3/src/dm/impls/plex/plexhdf5.c:868:58: warning: expression result unused [-Wunused-value] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /sandbox/petsc/petsc.next-3/src/dm/impls/plex/plexhdf5.c:868:41: warning: left-hand operand of comma expression has no effect [-Wunused-value] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /sandbox/petsc/petsc.next-3/src/dm/impls/plex/plexhdf5.c:868:78: warning: left-hand operand of comma expression has no effect [-Wunused-value] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /usr/home/balay/petsc.next/src/dm/impls/plex/plexhdf5.c:868:103: warning: right operand of comma operator has no effect [-Wunused-value] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /usr/home/balay/petsc.next/src/dm/impls/plex/plexhdf5.c:868:74: warning: right operand of comma operator has no effect [-Wunused-value] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /home/sandbox/petsc/petsc.next-3/src/dm/impls/plex/plexhdf5.c:868:58: warning: right operand of comma operator has no effect [-Wunused-value] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /sandbox/petsc/petsc.next-3/src/dm/impls/plex/plexhdf5.c:868:72: warning: left-hand operand of comma expression has no effect [-Wunused-value] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /home/sandbox/petsc/petsc.next-3/src/dm/impls/plex/plexhdf5.c:868:75: warning: right operand of comma operator has no effect [-Wunused-value] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /sandbox/petsc/petsc.next-2/src/dm/impls/plex/plexhdf5.c:868:78: warning: left-hand operand of comma expression has no effect [-Wunused-value] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /usr/home/balay/petsc.next/src/dm/impls/plex/plexhdf5.c:868:58: warning: right operand of comma operator has no effect [-Wunused-value] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /usr/home/balay/petsc.next/src/dm/impls/plex/plexhdf5.c:868:3: error: 'PetscStackCallHDF5' was not declared in this scope [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /usr/home/balay/petsc.next-2/src/dm/impls/plex/plexhdf5.c:868:103: warning: right operand of comma operator is a reference, not call, to function 'ReadLabelHDF5_Static' [-Waddress] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /home/sandbox/petsc/petsc.next-3/src/dm/impls/plex/plexhdf5.c:868:43: warning: left operand of comma operator has no effect [-Wunused-value] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /usr/home/balay/petsc.next-2/src/dm/impls/plex/plexhdf5.c:868:74: warning: right operand of comma operator has no effect [-Wunused-value] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /usr/home/balay/petsc.next/src/dm/impls/plex/plexhdf5.c:868:103: warning: right operand of comma operator is a reference, not call, to function 'ReadLabelHDF5_Static' [-Waddress] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /Users/petsc/petsc.next-3/src/dm/impls/plex/plexhdf5.c:868:34: warning: expression result unused [-Wunused-value] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /Users/petsc/petsc.next-3/src/dm/impls/plex/plexhdf5.c:868:43: warning: expression result unused [-Wunused-value] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /sandbox/petsc/petsc.next-2/src/dm/impls/plex/plexhdf5.c:868:78: warning: left-hand operand of comma expression has no effect [-Wunused-value] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /sandbox/petsc/petsc.next-3/src/dm/impls/plex/plexhdf5.c:868:100: warning: left-hand operand of comma expression has no effect [-Wunused-value] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /sandbox/petsc/petsc.next-2/src/dm/impls/plex/plexhdf5.c:868:41: warning: left-hand operand of comma expression has no effect [-Wunused-value] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /Users/petsc/petsc.next-3/src/dm/impls/plex/plexhdf5.c:868:74: warning: expression result unused [-Wunused-value] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /home/sandbox/petsc/petsc.next-3/src/dm/impls/plex/plexhdf5.c:868:103: warning: right operand of comma operator has no effect [-Wunused-value] src/dm/impls/plex/plexhdf5.c:869 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /Users/petsc/petsc.next-3/src/dm/impls/plex/plexhdf5.c:869:3: error: use of undeclared identifier 'PetscStackCallHDF5' ---- To opt-out from receiving these messages - send a request to petsc-dev(a)mcs.anl.gov.

2 1

PETSc blame digest (next) 2019-06-24
by PETSc checkBuilds 24 Jun '19

24 Jun '19

Dear PETSc developer, This email contains listings of contributions attributed to you by `git blame` that caused compiler errors or warnings in PETSc automated testing. Follow the links to see the full log files. Please attempt to fix the issues promptly or let us know at petsc-dev(a)mcs.anl.gov if you are unable to resolve the issues. Thanks, The PETSc development team ---- warnings attributed to commit https://bitbucket.org/petsc/petsc/commits/45ee418 makefile: add + to recursive recipes so that "make test" does not warn about -j lib/petsc/conf/rules:280 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /sandbox/petsc/petsc.next-3/lib/petsc/conf/rules:280: recipe for target 'ex47.PETSc' failed [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /sandbox/petsc/petsc.next-3/lib/petsc/conf/rules:280: recipe for target 'ex19.PETSc' failed lib/petsc/conf/rules:331 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /sandbox/petsc/petsc.next-3/lib/petsc/conf/rules:331: recipe for target 'ex5f.PETSc' failed ---- warnings attributed to commit https://bitbucket.org/petsc/petsc/commits/9d97c38 Alternate option for test makefile lib/petsc/conf/test:16 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /sandbox/petsc/petsc.next-3/lib/petsc/conf/test:16: recipe for target 'ex5f' failed ---- To opt-out from receiving these messages - send a request to petsc-dev(a)mcs.anl.gov.

1 0

PETSc blame digest (next) 2019-06-24
by PETSc checkBuilds 24 Jun '19

24 Jun '19

Dear PETSc developer, This email contains listings of contributions attributed to you by `git blame` that caused compiler errors or warnings in PETSc automated testing. Follow the links to see the full log files. Please attempt to fix the issues promptly or let us know at petsc-dev(a)mcs.anl.gov if you are unable to resolve the issues. Thanks, The PETSc development team ---- warnings attributed to commit https://bitbucket.org/petsc/petsc/commits/ef1fac7 Plex+HDF5: Write two cell arrays, one for normal and one for hybrid cells src/dm/impls/plex/plexhdf5.c:495 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /Users/petsc/petsc.next-3/src/dm/impls/plex/plexhdf5.c:495:3: error: use of undeclared identifier 'PetscStackCallHDF5' [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /usr/home/balay/petsc.next-2/src/dm/impls/plex/plexhdf5.c:495:3: error: 'PetscStackCallHDF5' was not declared in this scope [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /sandbox/petsc/petsc.next-2/src/dm/impls/plex/plexhdf5.c:495:3: warning: implicit declaration of function 'PetscStackCallHDF5' [-Wimplicit-function-declaration] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /sandbox/petsc/petsc.next-3/src/dm/impls/plex/plexhdf5.c:495:3: warning: implicit declaration of function 'PetscStackCallHDF5' [-Wimplicit-function-declaration] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /home/sandbox/petsc/petsc.next-3/src/dm/impls/plex/plexhdf5.c:495:40: error: 'PetscStackCallHDF5' was not declared in this scope [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /usr/home/balay/petsc.next/src/dm/impls/plex/plexhdf5.c:495:3: error: 'PetscStackCallHDF5' was not declared in this scope [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /sandbox/petsc/petsc.next-2/src/dm/impls/plex/plexhdf5.c:495:3: warning: implicit declaration of function 'PetscStackCallHDF5' [-Wimplicit-function-declaration] ---- To opt-out from receiving these messages - send a request to petsc-dev(a)mcs.anl.gov.

1 0

PETSc blame digest (next) 2019-06-24
by PETSc checkBuilds 24 Jun '19

24 Jun '19

Dear PETSc developer, This email contains listings of contributions attributed to you by `git blame` that caused compiler errors or warnings in PETSc automated testing. Follow the links to see the full log files. Please attempt to fix the issues promptly or let us know at petsc-dev(a)mcs.anl.gov if you are unable to resolve the issues. Thanks, The PETSc development team ---- warnings attributed to commit https://bitbucket.org/petsc/petsc/commits/729ab6d moved the rest of the HDF5 calls behind PetscStackCall's src/dm/impls/plex/plexhdf5.c:672 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /home/sandbox/petsc/petsc.next-3/src/dm/impls/plex/plexhdf5.c:672:40: error: 'PetscStackCallHDF5' was not declared in this scope [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /Users/petsc/petsc.next-3/src/dm/impls/plex/plexhdf5.c:672:3: error: use of undeclared identifier 'PetscStackCallHDF5' [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /usr/home/balay/petsc.next-2/src/dm/impls/plex/plexhdf5.c:672:3: error: 'PetscStackCallHDF5' was not declared in this scope [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /usr/home/balay/petsc.next/src/dm/impls/plex/plexhdf5.c:672:3: error: 'PetscStackCallHDF5' was not declared in this scope src/dm/impls/plex/plexhdf5.c:693 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /usr/home/balay/petsc.next/src/dm/impls/plex/plexhdf5.c:693:26: error: 'PetscStackCallHDF5' was not declared in this scope [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /Users/petsc/petsc.next-3/src/dm/impls/plex/plexhdf5.c:693:26: error: use of undeclared identifier 'PetscStackCallHDF5' [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /home/sandbox/petsc/petsc.next-3/src/dm/impls/plex/plexhdf5.c:693:63: error: 'PetscStackCallHDF5' was not declared in this scope [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /usr/home/balay/petsc.next-2/src/dm/impls/plex/plexhdf5.c:693:26: error: 'PetscStackCallHDF5' was not declared in this scope src/dm/impls/plex/plexhdf5.c:713 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /Users/petsc/petsc.next-3/src/dm/impls/plex/plexhdf5.c:713:28: error: use of undeclared identifier 'PetscStackCallHDF5' [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /usr/home/balay/petsc.next/src/dm/impls/plex/plexhdf5.c:713:28: error: 'PetscStackCallHDF5' was not declared in this scope [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /home/sandbox/petsc/petsc.next-3/src/dm/impls/plex/plexhdf5.c:713:65: error: 'PetscStackCallHDF5' was not declared in this scope [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/24/build_next…] /usr/home/balay/petsc.next-2/src/dm/impls/plex/plexhdf5.c:713:28: error: 'PetscStackCallHDF5' was not declared in this scope ---- To opt-out from receiving these messages - send a request to petsc-dev(a)mcs.anl.gov.

1 0

PETSc blame digest (next-tmp) 2019-06-23
by PETSc checkBuilds 23 Jun '19

23 Jun '19

Dear PETSc developer, This email contains listings of contributions attributed to you by `git blame` that caused compiler errors or warnings in PETSc automated testing. Follow the links to see the full log files. Please attempt to fix the issues promptly or let us know at petsc-dev(a)mcs.anl.gov if you are unable to resolve the issues. Thanks, The PETSc development team ---- warnings attributed to commit https://bitbucket.org/petsc/petsc/commits/09c5633 Non-numeric optimizations focused on AIJ, MatFDColoring, and DMCreateMatrix_DA_*AIJ, looking to improve performance in GPU environments src/mat/impls/aij/mpi/fdmpiaij.c:564 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/23/build_next…] /sandbox/petsc/petsc.next-tmp-2/src/mat/impls/aij/mpi/fdmpiaij.c:564:45: warning: 'tmp' may be used uninitialized in this function [-Wmaybe-uninitialized] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/23/build_next…] /sandbox/petsc/petsc.next-tmp-2/src/mat/impls/aij/mpi/fdmpiaij.c:564:45: warning: 'tmp' may be used uninitialized in this function [-Wmaybe-uninitialized] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/23/build_next…] /sandbox/petsc/petsc.next-tmp/src/mat/impls/aij/mpi/fdmpiaij.c:564:45: warning: 'tmp' may be used uninitialized in this function [-Wmaybe-uninitialized] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/23/build_next…] /sandbox/petsc/petsc.next-tmp-3/src/mat/impls/aij/mpi/fdmpiaij.c:564:45: warning: 'tmp' may be used uninitialized in this function [-Wmaybe-uninitialized] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/23/build_next…] /sandbox/petsc/petsc.next-tmp-2/src/mat/impls/aij/mpi/fdmpiaij.c:564:45: warning: 'tmp' may be used uninitialized in this function [-Wmaybe-uninitialized] src/mat/impls/aij/seq/seqviennacl/aijviennacl.cxx:130 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/23/build_next…] /sandbox/petsc/petsc.next-tmp-2/src/mat/impls/aij/seq/seqviennacl/aijviennacl.cxx:130:34: error: 'PetscFree1' was not declared in this scope ---- To opt-out from receiving these messages - send a request to petsc-dev(a)mcs.anl.gov.

2 1

PETSc blame digest (next-tmp) 2019-06-23
by PETSc checkBuilds 23 Jun '19

23 Jun '19

Dear PETSc developer, This email contains listings of contributions attributed to you by `git blame` that caused compiler errors or warnings in PETSc automated testing. Follow the links to see the full log files. Please attempt to fix the issues promptly or let us know at petsc-dev(a)mcs.anl.gov if you are unable to resolve the issues. Thanks, The PETSc development team ---- warnings attributed to commit https://bitbucket.org/petsc/petsc/commits/d7e70f4 tests: attempt to speedup builds/tests by using MAKE_LOAD [set higher than NPMAX] lib/petsc/conf/rules:43 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/23/build_next…] /sandbox/petsc/petsc.next-tmp-2/lib/petsc/conf/rules:43: recipe for target 'libs' failed ---- To opt-out from receiving these messages - send a request to petsc-dev(a)mcs.anl.gov.

1 0

PETSc blame digest (next-tmp) 2019-06-22
by PETSc checkBuilds 22 Jun '19

22 Jun '19

Dear PETSc developer, This email contains listings of contributions attributed to you by `git blame` that caused compiler errors or warnings in PETSc automated testing. Follow the links to see the full log files. Please attempt to fix the issues promptly or let us know at petsc-dev(a)mcs.anl.gov if you are unable to resolve the issues. Thanks, The PETSc development team ---- warnings attributed to commit https://bitbucket.org/petsc/petsc/commits/09c5633 Non-numeric optimizations focused on AIJ, MatFDColoring, and DMCreateMatrix_DA_*AIJ, looking to improve performance in GPU environments src/mat/impls/aij/mpi/fdmpiaij.c:564 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/22/build_next…] /sandbox/petsc/petsc.next-tmp/src/mat/impls/aij/mpi/fdmpiaij.c:564:45: warning: 'tmp' may be used uninitialized in this function [-Wmaybe-uninitialized] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/22/build_next…] /sandbox/petsc/petsc.next-tmp-2/src/mat/impls/aij/mpi/fdmpiaij.c:564:45: warning: 'tmp' may be used uninitialized in this function [-Wmaybe-uninitialized] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/22/build_next…] /sandbox/petsc/petsc.next-tmp-3/src/mat/impls/aij/mpi/fdmpiaij.c:564:45: warning: 'tmp' may be used uninitialized in this function [-Wmaybe-uninitialized] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/22/build_next…] /sandbox/petsc/petsc.next-tmp-2/src/mat/impls/aij/mpi/fdmpiaij.c:564:45: warning: 'tmp' may be used uninitialized in this function [-Wmaybe-uninitialized] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/22/build_next…] /sandbox/petsc/petsc.next-tmp-2/src/mat/impls/aij/mpi/fdmpiaij.c:564:45: warning: 'tmp' may be used uninitialized in this function [-Wmaybe-uninitialized] src/mat/impls/aij/seq/seqviennacl/aijviennacl.cxx:130 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/22/build_next…] /sandbox/petsc/petsc.next-tmp-2/src/mat/impls/aij/seq/seqviennacl/aijviennacl.cxx:130:34: error: 'PetscFree1' was not declared in this scope ---- To opt-out from receiving these messages - send a request to petsc-dev(a)mcs.anl.gov.

2 1