PETSc blame digest (next-tmp) 2019-07-26
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/8361489 basic function evaluation working for cuda nonlinear function example on ONE process only src/snes/examples/tutorials/ex47cu.cu:110 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/07/26/examples_ne...] /sandbox/petsc/petsc.next-tmp/src/snes/examples/tutorials/ex47cu.cu:110:803: warning: ISO C++ says that these are ambiguous, even though the worst conversion for the first is better than the worst conversion for the second: [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/07/26/examples_ne...] /sandbox/petsc/petsc.next-tmp-3/src/snes/examples/tutorials/ex47cu.cu:110:803: warning: ISO C++ says that these are ambiguous, even though the worst conversion for the first is better than the worst conversion for the second: ---- To opt-out from receiving these messages - send a request to [email protected].
participants (1)
-
PETSc checkBuilds