PETSc blame digest (next) 2018-01-30
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 [email protected] if you are unable to resolve the issues. Thanks, The PETSc development team ---- warnings attributed to commit https://bitbucket.org/petsc/petsc/commits/23f935d VecScatter: More rigorous checking for integer overflows. src/vec/vec/utils/vpscat.c:2678 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/01/30/build_next_a...] "/export/home/petsc/petsc.next-2/src/vec/vec/utils/vpscat.c", line 2678: warning: argument #3 is incompatible with prototype: [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/01/30/build_next_a...] /sandbox/petsc/petsc.next-2/src/vec/vec/utils/vpscat.c:2678:12: error: no matching function for call to 'PetscIntMultError' [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/01/30/build_next_a...] /sandbox/petsc/petsc.next-3/src/vec/vec/utils/vpscat.c:2678:5: warning: passing argument 3 of 'PetscIntMultError' from incompatible pointer type [enabled by default] ---- To opt-out from receiving these messages - send a request to [email protected].
participants (1)
-
PETSc checkBuilds