July 2018 - petsc-checkbuilds - mailman3.cels.anl.gov

PETSc blame digest (next-tmp) 2018-07-20
by PETSc checkBuilds 20 Jul '18

20 Jul '18

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/6f15834 Plex+PCPatch: Converted to IS input and Toby's geometry src/ksp/pc/impls/patch/pcpatch.c:1262 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/20/build_next-…] /home/sandbox/petsc/petsc.next-tmp-3/src/ksp/pc/impls/patch/pcpatch.c:1262: undefined reference to `DMPlexComputeJacobian_Patch_Internal' ---- To opt-out from receiving these messages - send a request to petsc-dev(a)mcs.anl.gov.

1 0

PETSc blame digest (next-tmp) 2018-07-19
by PETSc checkBuilds 19 Jul '18

19 Jul '18

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/60d94c4 Add a shared memory vecscatter using point-to-point synchronization src/vec/vscat/impls/vpscat_mpi1.h:173 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/19/build_next-…] /sandbox/petsc/petsc.next-tmp-3/include/../src/vec/vscat/impls/vpscat_mpi1.h:173:9: warning: implicit declaration of function 'PETSC_WRITE_MEMORY_BARRIER'; did you mean 'PETSC_HAVE_MPI_IBARRIER'? [-Wimplicit-function-declaration] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/19/build_next-…] /sandbox/petsc/petsc.next-tmp/include/../src/vec/vscat/impls/vpscat_mpi1.h:173:9: warning: implicit declaration of function 'PETSC_WRITE_MEMORY_BARRIER'; did you mean 'PETSC_HAVE_MPI_IBARRIER'? [-Wimplicit-function-declaration] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/19/build_next-…] /sandbox/petsc/petsc.next-tmp-2/include/../src/vec/vscat/impls/vpscat_mpi1.h:173:9: error: 'PETSC_WRITE_MEMORY_BARRIER' 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) 2018-07-18
by PETSc checkBuilds 18 Jul '18

18 Jul '18

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/293d5d1 Revise PETSc shared memory communicator keyval interface src/sys/objects/tagm.c:437 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/18/build_next-…] /sandbox/petsc/petsc.next-tmp-2/src/sys/objects/tagm.c:437:12: error: 'MPI_PROC_NULL' undeclared (first use in this function) src/sys/objects/tagm.c:477 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/18/build_next-…] /home/sandbox/petsc/petsc.next-tmp-2/src/sys/objects/tagm.c:477:3: warning: ISO C90 forbids mixed declarations and code [-Wpedantic] ---- warnings attributed to commit https://bitbucket.org/petsc/petsc/commits/a2f00be Add a shared memory vecscatter using point-to-point synchronization src/vec/vscat/impls/vpscat_mpi1.c:2692 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/18/build_next-…] /home/sandbox/petsc/petsc.next-tmp-2/src/vec/vscat/impls/vpscat_mpi1.c:2692:5: warning: ISO C90 forbids mixed declarations and code [-Wpedantic] src/vec/vscat/impls/vpscat_mpi1.c:434 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/18/build_next-…] /home/sandbox/petsc/petsc.next-tmp-2/src/vec/vscat/impls/vpscat_mpi1.c:434:5: warning: ISO C90 forbids mixed declarations and code [-Wpedantic] src/vec/vscat/impls/vpscat_mpi1.c:450 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/18/build_next-…] /home/sandbox/petsc/petsc.next-tmp-2/src/vec/vscat/impls/vpscat_mpi1.c:450:5: warning: ISO C90 forbids mixed declarations and code [-Wpedantic] src/vec/vscat/impls/vpscat_mpi1.c:456 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/18/build_next-…] /home/sandbox/petsc/petsc.next-tmp-2/src/vec/vscat/impls/vpscat_mpi1.c:456:5: warning: ISO C90 forbids mixed declarations and code [-Wpedantic] src/vec/vscat/impls/vpscat_mpi1.h:173 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/18/build_next-…] /sandbox/petsc/petsc.next-tmp/include/../src/vec/vscat/impls/vpscat_mpi1.h:173:9: warning: implicit declaration of function 'PETSC_WRITE_MEMORY_BARRIER'; did you mean 'PETSC_HAVE_MPI_IBARRIER'? [-Wimplicit-function-declaration] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/18/build_next-…] /sandbox/petsc/petsc.next-tmp-2/include/../src/vec/vscat/impls/vpscat_mpi1.h:173:9: error: 'PETSC_WRITE_MEMORY_BARRIER' was not declared in this scope [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/18/build_next-…] /sandbox/petsc/petsc.next-tmp-3/include/../src/vec/vscat/impls/vpscat_mpi1.h:173:9: warning: implicit declaration of function 'PETSC_WRITE_MEMORY_BARRIER'; did you mean 'PETSC_HAVE_MPI_IBARRIER'? [-Wimplicit-function-declaration] src/vec/vscat/impls/vpscat_mpi1.h:243 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/18/build_next-…] /home/sandbox/petsc/petsc.next-tmp-2/include/../src/vec/vscat/impls/vpscat_mpi1.h:243:3: warning: ISO C90 forbids mixed declarations and code [-Wpedantic] ---- To opt-out from receiving these messages - send a request to petsc-dev(a)mcs.anl.gov.

1 0

PETSc blame digest (next-tmp) 2018-07-18
by PETSc checkBuilds 18 Jul '18

18 Jul '18

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/4e78640 bk-changeset-1.3552.1.11 include/petsc/private/petscimpl.h:450 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/18/build_next-…] /sandbox/petsc/petsc.next-tmp/include/petsc/private/petscimpl.h:450:54: warning: right-hand operand of comma expression has no effect [-Wunused-value] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/18/build_next-…] /usr/home/balay/petsc.next-tmp-3/include/petsc/private/petscimpl.h:450:54: warning: right-hand operand of comma expression has no effect [-Wunused-value] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/18/build_next-…] /sandbox/petsc/petsc.next-tmp-3/include/petsc/private/petscimpl.h:450:54: warning: right-hand operand of comma expression has no effect [-Wunused-value] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/18/build_next-…] /sandbox/petsc/petsc.next-tmp-3/include/petsc/private/petscimpl.h:450:54: warning: right-hand operand of comma expression has no effect [-Wunused-value] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/18/build_next-…] /sandbox/petsc/petsc.next-tmp-3/include/petsc/private/petscimpl.h:450:54: warning: right-hand operand of comma expression has no effect [-Wunused-value] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/18/build_next-…] /sandbox/petsc/petsc.next-tmp/include/petsc/private/petscimpl.h:450:54: warning: right-hand operand of comma expression has no effect [-Wunused-value] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/18/build_next-…] /sandbox/petsc/petsc.next-tmp-2/include/petsc/private/petscimpl.h:450:54: warning: right-hand operand of comma expression has no effect [-Wunused-value] ---- To opt-out from receiving these messages - send a request to petsc-dev(a)mcs.anl.gov.

1 0

PETSc blame digest (next-tmp) 2018-07-18
by PETSc checkBuilds 18 Jul '18

18 Jul '18

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/4bbf5ea PCPatch: Initial checkin include/petsc/private/pcpatchimpl.h:81 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/18/build_next-…] "/export/home/petsc/petsc.next-tmp-3/include/petsc/private/pcpatchimpl.h", line 81: warning: linker scope was specified more than once: "PC_Patch_Prealloc" [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/18/build_next-…] "/export/home/petsc/petsc.next-tmp/include/petsc/private/pcpatchimpl.h", line 81: warning: linker scope was specified more than once: "PC_Patch_Apply" [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/18/build_next-…] "/export/home/petsc/petsc.next-tmp-2/include/petsc/private/pcpatchimpl.h", line 81: warning: linker scope was specified more than once: "PC_Patch_Scatter" [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/18/build_next-…] "/export/home/petsc/petsc.next-tmp-3/include/petsc/private/pcpatchimpl.h", line 81: warning: linker scope was specified more than once: "PC_Patch_Scatter" [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/18/build_next-…] "/export/home/petsc/petsc.next-tmp-2/include/petsc/private/pcpatchimpl.h", line 81: warning: linker scope was specified more than once: "PC_Patch_ComputeOp" [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/18/build_next-…] "/export/home/petsc/petsc.next-tmp-3/include/petsc/private/pcpatchimpl.h", line 81: warning: linker scope was specified more than once: "PC_Patch_ComputeOp" [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/18/build_next-…] "/export/home/petsc/petsc.next-tmp/include/petsc/private/pcpatchimpl.h", line 81: warning: linker scope was specified more than once: "PC_Patch_Scatter" [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/18/build_next-…] "/export/home/petsc/petsc.next-tmp-3/include/petsc/private/pcpatchimpl.h", line 81: warning: linker scope was specified more than once: "PC_Patch_Apply" [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/18/build_next-…] "/export/home/petsc/petsc.next-tmp-2/include/petsc/private/pcpatchimpl.h", line 81: warning: linker scope was specified more than once: "PC_Patch_Apply" [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/18/build_next-…] "/export/home/petsc/petsc.next-tmp-3/include/petsc/private/pcpatchimpl.h", line 81: warning: linker scope was specified more than once: "PC_Patch_Solve" [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/18/build_next-…] "/export/home/petsc/petsc.next-tmp/include/petsc/private/pcpatchimpl.h", line 81: warning: linker scope was specified more than once: "PC_Patch_ComputeOp" [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/18/build_next-…] "/export/home/petsc/petsc.next-tmp-2/include/petsc/private/pcpatchimpl.h", line 81: warning: linker scope was specified more than once: "PC_Patch_Prealloc" [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/18/build_next-…] "/export/home/petsc/petsc.next-tmp/include/petsc/private/pcpatchimpl.h", line 81: warning: linker scope was specified more than once: "PC_Patch_Solve" [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/18/build_next-…] "/export/home/petsc/petsc.next-tmp-2/include/petsc/private/pcpatchimpl.h", line 81: warning: linker scope was specified more than once: "PC_Patch_Solve" [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/18/build_next-…] "/export/home/petsc/petsc.next-tmp/include/petsc/private/pcpatchimpl.h", line 81: warning: linker scope was specified more than once: "PC_Patch_Prealloc" ---- warnings attributed to commit https://bitbucket.org/petsc/petsc/commits/6f15834 Plex+PCPatch: Converted to IS input and Toby's geometry src/ksp/pc/impls/patch/pcpatch.c:1262 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/18/build_next-…] /home/sandbox/petsc/petsc.next-tmp-3/src/ksp/pc/impls/patch/pcpatch.c:1262: undefined reference to `DMPlexComputeJacobian_Patch_Internal' ---- To opt-out from receiving these messages - send a request to petsc-dev(a)mcs.anl.gov.

1 0

PETSc blame digest (next) 2018-07-16
by PETSc checkBuilds 16 Jul '18

16 Jul '18

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/c69f721 Added MatZeroEntries_HYPRE src/mat/impls/hypre/mhypre.c:1103 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/16/build_next_…] /home/sandbox/petsc/petsc.next/src/mat/impls/hypre/mhypre.c:1103:53: warning: 'array' may be used uninitialized in this function [-Wmaybe-uninitialized] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/16/build_next_…] /sandbox/petsc/petsc.next/src/mat/impls/hypre/mhypre.c:1103:53: warning: 'array' may be used uninitialized in this function [-Wmaybe-uninitialized] src/mat/impls/hypre/mhypre.c:1105 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/16/build_next_…] /sandbox/petsc/petsc.next-3/src/mat/impls/hypre/mhypre.c:1105:9: warning: passing argument 3 of 'HYPRE_IJMatrixSetValues' from incompatible pointer type [enabled by default] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/16/build_next_…] /sandbox/petsc/petsc.next-3/src/mat/impls/hypre/mhypre.c:1105:9: warning: passing argument 5 of 'HYPRE_IJMatrixSetValues' from incompatible pointer type [enabled by default] src/mat/impls/hypre/mhypre.c:1524 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/16/build_next_…] /sandbox/petsc/petsc.next-3/src/mat/impls/hypre/mhypre.c:1524:5: warning: assignment from incompatible pointer type [enabled by default] src/mat/impls/hypre/mhypre.c:1525 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/16/build_next_…] /sandbox/petsc/petsc.next-3/src/mat/impls/hypre/mhypre.c:1525:5: warning: assignment from incompatible pointer type [enabled by default] src/mat/impls/hypre/mhypre.c:1582 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/16/build_next_…] /sandbox/petsc/petsc.next-3/src/mat/impls/hypre/mhypre.c:1582:3: warning: passing argument 4 of 'HYPRE_ParCSRMatrixGetRow' from incompatible pointer type [enabled by default] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/16/build_next_…] /sandbox/petsc/petsc.next-3/src/mat/impls/hypre/mhypre.c:1582:3: warning: passing argument 3 of 'HYPRE_ParCSRMatrixGetRow' from incompatible pointer type [enabled by default] src/mat/impls/hypre/mhypre.c:1595 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/16/build_next_…] /sandbox/petsc/petsc.next-3/src/mat/impls/hypre/mhypre.c:1595:3: warning: passing argument 4 of 'HYPRE_ParCSRMatrixRestoreRow' from incompatible pointer type [enabled by default] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/16/build_next_…] /sandbox/petsc/petsc.next-3/src/mat/impls/hypre/mhypre.c:1595:3: warning: passing argument 3 of 'HYPRE_ParCSRMatrixRestoreRow' from incompatible pointer type [enabled by default] src/mat/impls/hypre/mhypre.c:1613 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/16/build_next_…] /sandbox/petsc/petsc.next-3/src/mat/impls/hypre/mhypre.c:1613:5: warning: passing argument 3 of 'HYPRE_IJMatrixGetValues' from incompatible pointer type [enabled by default] ---- To opt-out from receiving these messages - send a request to petsc-dev(a)mcs.anl.gov.

5 10

PETSc blame digest (next) 2018-07-16
by PETSc checkBuilds 16 Jul '18

16 Jul '18

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/7d96882 MatHYPRE: fix warnings from nightly builds with 64bit indices src/mat/impls/hypre/mhypre.c:1089 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/16/build_next_…] /sandbox/petsc/petsc.next-3/src/mat/impls/hypre/mhypre.c:1089:9: warning: passing argument 5 of 'HYPRE_IJMatrixAddToValues' from incompatible pointer type [enabled by default] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/16/build_next_…] /sandbox/petsc/petsc.next-3/src/mat/impls/hypre/mhypre.c:1089:9: warning: passing argument 3 of 'HYPRE_IJMatrixAddToValues' from incompatible pointer type [enabled by default] ---- warnings attributed to commit https://bitbucket.org/petsc/petsc/commits/d975228 Added support for SetValues and Preallocation src/mat/impls/hypre/mhypre.c:1075 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/16/build_next_…] /usr/home/balay/petsc.next-3/src/mat/impls/hypre/mhypre.c:1075:14: warning: 'array' may be used uninitialized in this function [-Wmaybe-uninitialized] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/16/build_next_…] /usr/home/balay/petsc.next-2/src/mat/impls/hypre/mhypre.c:1075:20: warning: 'array' 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-tmp) 2018-07-02
by PETSc checkBuilds 02 Jul '18

02 Jul '18

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/59a3400 fixed handling of byte swaps for __float128 include/petscsys.h:1422 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/02/build_next-…] /sandbox/petsc/petsc.next-tmp-3/include/petscsys.h:1422:24: warning: passing argument 3 of 'DMRestoreWorkArray' makes pointer from integer without a cast [-Wint-conversion] ---- To opt-out from receiving these messages - send a request to petsc-dev(a)mcs.anl.gov.

1 0

PETSc blame digest (next-tmp) 2018-07-02
by PETSc checkBuilds 02 Jul '18

02 Jul '18

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/4bbf5ea PCPatch: Initial checkin include/petsc/private/pcpatchimpl.h:81 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/02/build_next-…] "/export/home/petsc/petsc.next-tmp-2/include/petsc/private/pcpatchimpl.h", line 81: warning: linker scope was specified more than once: "PC_Patch_Prealloc" [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/02/build_next-…] "/export/home/petsc/petsc.next-tmp-3/include/petsc/private/pcpatchimpl.h", line 81: warning: linker scope was specified more than once: "PC_Patch_Prealloc" [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/02/build_next-…] "/export/home/petsc/petsc.next-tmp-2/include/petsc/private/pcpatchimpl.h", line 81: warning: linker scope was specified more than once: "PC_Patch_Apply" [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/02/build_next-…] "/export/home/petsc/petsc.next-tmp/include/petsc/private/pcpatchimpl.h", line 81: warning: linker scope was specified more than once: "PC_Patch_Prealloc" [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/02/build_next-…] "/export/home/petsc/petsc.next-tmp/include/petsc/private/pcpatchimpl.h", line 81: warning: linker scope was specified more than once: "PC_Patch_Solve" [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/02/build_next-…] "/export/home/petsc/petsc.next-tmp/include/petsc/private/pcpatchimpl.h", line 81: warning: linker scope was specified more than once: "PC_Patch_ComputeOp" [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/02/build_next-…] "/export/home/petsc/petsc.next-tmp-3/include/petsc/private/pcpatchimpl.h", line 81: warning: linker scope was specified more than once: "PC_Patch_Apply" [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/02/build_next-…] "/export/home/petsc/petsc.next-tmp-3/include/petsc/private/pcpatchimpl.h", line 81: warning: linker scope was specified more than once: "PC_Patch_ComputeOp" [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/02/build_next-…] "/export/home/petsc/petsc.next-tmp-3/include/petsc/private/pcpatchimpl.h", line 81: warning: linker scope was specified more than once: "PC_Patch_Scatter" [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/02/build_next-…] "/export/home/petsc/petsc.next-tmp/include/petsc/private/pcpatchimpl.h", line 81: warning: linker scope was specified more than once: "PC_Patch_Scatter" [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/02/build_next-…] "/export/home/petsc/petsc.next-tmp-2/include/petsc/private/pcpatchimpl.h", line 81: warning: linker scope was specified more than once: "PC_Patch_Scatter" [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/02/build_next-…] "/export/home/petsc/petsc.next-tmp-3/include/petsc/private/pcpatchimpl.h", line 81: warning: linker scope was specified more than once: "PC_Patch_Solve" [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/02/build_next-…] "/export/home/petsc/petsc.next-tmp-2/include/petsc/private/pcpatchimpl.h", line 81: warning: linker scope was specified more than once: "PC_Patch_Solve" [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/02/build_next-…] "/export/home/petsc/petsc.next-tmp-2/include/petsc/private/pcpatchimpl.h", line 81: warning: linker scope was specified more than once: "PC_Patch_ComputeOp" [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/02/build_next-…] "/export/home/petsc/petsc.next-tmp/include/petsc/private/pcpatchimpl.h", line 81: warning: linker scope was specified more than once: "PC_Patch_Apply" ---- warnings attributed to commit https://bitbucket.org/petsc/petsc/commits/6f15834 Plex+PCPatch: Converted to IS input and Toby's geometry src/ksp/pc/impls/patch/pcpatch.c:1262 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/02/build_next-…] /home/sandbox/petsc/petsc.next-tmp-3/src/ksp/pc/impls/patch/pcpatch.c:1262: undefined reference to `DMPlexComputeJacobian_Patch_Internal' ---- warnings attributed to commit https://bitbucket.org/petsc/petsc/commits/f7e6ed9 Plex: Added DMPlexComputeJacobian_Patch_Internal() src/snes/utils/dmplexsnes.c:2469 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/02/build_next-…] /home/sandbox/petsc/petsc.next-tmp-2/src/snes/utils/dmplexsnes.c:2469:3: warning: passing argument 3 of 'DMRestoreWorkArray' makes pointer from integer without a cast [enabled by default] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/02/build_next-…] /sandbox/petsc/petsc.next-tmp-3/src/snes/utils/dmplexsnes.c:2469:3: warning: passing argument 3 of 'DMRestoreWorkArray' makes pointer from integer without a cast [enabled by default] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/02/build_next-…] /sandbox/petsc/petsc.next-tmp-3/src/snes/utils/dmplexsnes.c:2469:37: warning: passing argument 3 of 'DMRestoreWorkArray' makes pointer from integer without a cast [-Wint-conversion] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/02/build_next-…] /sandbox/petsc/petsc.next-tmp/src/snes/utils/dmplexsnes.c:2469:3: warning: passing argument 3 of 'DMRestoreWorkArray' makes pointer from integer without a cast [enabled by default] src/snes/utils/dmplexsnes.c:2470 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/02/build_next-…] /sandbox/petsc/petsc.next-tmp/src/snes/utils/dmplexsnes.c:2470:3: warning: passing argument 3 of 'DMRestoreWorkArray' makes pointer from integer without a cast [enabled by default] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/02/build_next-…] /home/sandbox/petsc/petsc.next-tmp-2/src/snes/utils/dmplexsnes.c:2470:3: warning: passing argument 3 of 'DMRestoreWorkArray' makes pointer from integer without a cast [enabled by default] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/02/build_next-…] /sandbox/petsc/petsc.next-tmp-3/src/snes/utils/dmplexsnes.c:2470:3: warning: passing argument 3 of 'DMRestoreWorkArray' makes pointer from integer without a cast [enabled by default] ---- To opt-out from receiving these messages - send a request to petsc-dev(a)mcs.anl.gov.

1 0

PETSc blame digest (next) 2018-07-01
by PETSc checkBuilds 01 Jul '18

01 Jul '18

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/7c3cd84 DMDA: Implement DMGetCompatibility src/dm/impls/da/da.c:1386 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/01/build_next_…] /sandbox/petsc/petsc.next/src/dm/impls/da/da.c:1386:21: error: cannot convert 'bool' to 'PetscBool' in assignment [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/01/build_next_…] /Users/petsc/petsc.next-2/src/dm/impls/da/da.c:1386:32: error: assigning to 'PetscBool' from incompatible type 'bool' [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/01/build_next_…] /usr/home/balay/petsc.next/src/dm/impls/da/da.c:1386:21: error: cannot convert 'bool' to 'PetscBool' in assignment src/dm/impls/da/da.c:1387 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/01/build_next_…] /usr/home/balay/petsc.next/src/dm/impls/da/da.c:1387:42: error: invalid conversion from 'int' to 'PetscBool' [-fpermissive] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/01/build_next_…] /sandbox/petsc/petsc.next/src/dm/impls/da/da.c:1387:42: error: invalid conversion from 'int' to 'PetscBool' [-fpermissive] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/01/build_next_…] /Users/petsc/petsc.next-2/src/dm/impls/da/da.c:1387:42: error: assigning to 'PetscBool' from incompatible type 'int' src/dm/impls/da/da.c:1388 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/01/build_next_…] /sandbox/petsc/petsc.next/src/dm/impls/da/da.c:1388:42: error: invalid conversion from 'int' to 'PetscBool' [-fpermissive] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/01/build_next_…] /usr/home/balay/petsc.next/src/dm/impls/da/da.c:1388:42: error: invalid conversion from 'int' to 'PetscBool' [-fpermissive] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/01/build_next_…] /Users/petsc/petsc.next-2/src/dm/impls/da/da.c:1388:42: error: assigning to 'PetscBool' from incompatible type 'int' src/dm/impls/da/da.c:1392 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/01/build_next_…] /Users/petsc/petsc.next-2/src/dm/impls/da/da.c:1392:58: error: assigning to 'PetscBool' from incompatible type 'int' [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/01/build_next_…] /sandbox/petsc/petsc.next/src/dm/impls/da/da.c:1392:58: error: invalid conversion from 'int' to 'PetscBool' [-fpermissive] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/01/build_next_…] /usr/home/balay/petsc.next/src/dm/impls/da/da.c:1392:58: error: invalid conversion from 'int' to 'PetscBool' [-fpermissive] src/dm/impls/da/da.c:1396 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/01/build_next_…] /sandbox/petsc/petsc.next/src/dm/impls/da/da.c:1396:58: error: invalid conversion from 'int' to 'PetscBool' [-fpermissive] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/01/build_next_…] /usr/home/balay/petsc.next/src/dm/impls/da/da.c:1396:58: error: invalid conversion from 'int' to 'PetscBool' [-fpermissive] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/01/build_next_…] /Users/petsc/petsc.next-2/src/dm/impls/da/da.c:1396:58: error: assigning to 'PetscBool' from incompatible type 'int' src/dm/impls/da/da.c:1402 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/01/build_next_…] /Users/petsc/petsc.next-2/src/dm/impls/da/da.c:1402:25: error: assigning to 'PetscBool' from incompatible type 'int' [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/01/build_next_…] /sandbox/petsc/petsc.next/src/dm/impls/da/da.c:1402:25: error: invalid conversion from 'int' to 'PetscBool' [-fpermissive] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/01/build_next_…] /usr/home/balay/petsc.next/src/dm/impls/da/da.c:1402:25: error: invalid conversion from 'int' to 'PetscBool' [-fpermissive] src/dm/impls/da/da.c:1407 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/01/build_next_…] /sandbox/petsc/petsc.next/src/dm/impls/da/da.c:1407:25: error: invalid conversion from 'int' to 'PetscBool' [-fpermissive] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/01/build_next_…] /usr/home/balay/petsc.next/src/dm/impls/da/da.c:1407:25: error: invalid conversion from 'int' to 'PetscBool' [-fpermissive] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/01/build_next_…] /Users/petsc/petsc.next-2/src/dm/impls/da/da.c:1407:25: error: assigning to 'PetscBool' from incompatible type 'int' src/dm/impls/da/da.c:1412 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/01/build_next_…] /sandbox/petsc/petsc.next/src/dm/impls/da/da.c:1412:25: error: invalid conversion from 'int' to 'PetscBool' [-fpermissive] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/01/build_next_…] /Users/petsc/petsc.next-2/src/dm/impls/da/da.c:1412:25: error: assigning to 'PetscBool' from incompatible type 'int' [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/07/01/build_next_…] /usr/home/balay/petsc.next/src/dm/impls/da/da.c:1412:25: error: invalid conversion from 'int' to 'PetscBool' [-fpermissive] ---- To opt-out from receiving these messages - send a request to petsc-dev(a)mcs.anl.gov.

1 0