PETSc blame digest (next) 2015-07-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/a9603a1 Allow the use of a custom H0 in LMVM/BLMVM. src/tao/interface/taosolver.c:2810 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2015/07/30/build_next_a...] /sandbox/petsc/petsc.clone-2/src/tao/interface/taosolver.c:2810:12: warning: passing argument 3 of 'VecDot' from incompatible pointer type [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2015/07/30/build_next_a...] /Users/petsc/petsc.clone-3/src/tao/interface/taosolver.c:2810: error: cannot convert 'PetscReal*' to 'PetscScalar*' for argument '3' to 'PetscErrorCode VecDot(_p_Vec*, _p_Vec*, PetscScalar*)' [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2015/07/30/build_next_a...] "/export/home/petsc/petsc.clone-3/src/tao/interface/taosolver.c", line 2810: warning: argument #3 is incompatible with prototype: [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2015/07/30/build_next_a...] /home/balay/petsc.clone-3/src/tao/interface/taosolver.c:2810:58: error: cannot convert 'PetscReal* {aka double*}' to 'PetscScalar* {aka std::complex<double>*}' for argument '3' to 'PetscErrorCode VecDot(Vec, Vec, PetscScalar*)' [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2015/07/30/build_next_a...] /sandbox/petsc/petsc.clone-2/src/tao/interface/taosolver.c:2810:12: error: no matching function for call to 'VecDot' ---- To opt-out from receiving these messages - send a request to [email protected].
Hi, I pushed a speculative fix (I can't reproduce myself). In general is there some way I can check turn on these extra-zealous checks, to shorten the debug cycle? Patrick On 30/07/15 15:00, PETSc checkBuilds wrote:
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/a9603a1 Allow the use of a custom H0 in LMVM/BLMVM.
src/tao/interface/taosolver.c:2810 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2015/07/30/build_next_a...] /sandbox/petsc/petsc.clone-2/src/tao/interface/taosolver.c:2810:12: warning: passing argument 3 of 'VecDot' from incompatible pointer type [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2015/07/30/build_next_a...] /Users/petsc/petsc.clone-3/src/tao/interface/taosolver.c:2810: error: cannot convert 'PetscReal*' to 'PetscScalar*' for argument '3' to 'PetscErrorCode VecDot(_p_Vec*, _p_Vec*, PetscScalar*)' [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2015/07/30/build_next_a...] "/export/home/petsc/petsc.clone-3/src/tao/interface/taosolver.c", line 2810: warning: argument #3 is incompatible with prototype: [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2015/07/30/build_next_a...] /home/balay/petsc.clone-3/src/tao/interface/taosolver.c:2810:58: error: cannot convert 'PetscReal* {aka double*}' to 'PetscScalar* {aka std::complex<double>*}' for argument '3' to 'PetscErrorCode VecDot(Vec, Vec, PetscScalar*)' [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2015/07/30/build_next_a...] /sandbox/petsc/petsc.clone-2/src/tao/interface/taosolver.c:2810:12: error: no matching function for call to 'VecDot'
---- To opt-out from receiving these messages - send a request to [email protected].
participants (2)
-
Patrick Farrell -
PETSc checkBuilds