August 2017 - petsc-checkbuilds - mailman3.cels.anl.gov

PETSc blame digest (next) 2017-08-29
by PETSc checkBuilds 29 Aug '17

29 Aug '17

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/a6c4b7b VecView_Network() works only with ASCII viewer; enable other formats using VecView_Seq/MPI() src/dm/impls/network/networkcreate.c:231 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/29/build_next_…] /sandbox/petsc/petsc.clone/src/dm/impls/network/networkcreate.c:231: undefined reference to `VecView_Seq(_p_Vec*, _p_PetscViewer*)' [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/29/build_next_…] /sandbox/petsc/petsc.clone-3/src/dm/impls/network/networkcreate.c:231: undefined reference to `VecView_Seq(_p_Vec*, _p_PetscViewer*)' src/dm/impls/network/networkcreate.c:233 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/29/build_next_…] /sandbox/petsc/petsc.clone/src/dm/impls/network/networkcreate.c:233: undefined reference to `VecView_MPI(_p_Vec*, _p_PetscViewer*)' [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/29/build_next_…] /sandbox/petsc/petsc.clone-3/src/dm/impls/network/networkcreate.c:233: undefined reference to `VecView_MPI(_p_Vec*, _p_PetscViewer*)' ---- To opt-out from receiving these messages - send a request to petsc-dev(a)mcs.anl.gov.

1 0

PETSc blame digest (next) 2017-08-26
by PETSc checkBuilds 26 Aug '17

26 Aug '17

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/f4a5305 *** empty log message *** src/mat/impls/maij/maij.c:3387 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/26/build_next_…] /sandbox/petsc/petsc.clone-4/src/mat/impls/maij/maij.c:3387:5: error: expected ';' before '}' token ---- To opt-out from receiving these messages - send a request to petsc-dev(a)mcs.anl.gov.

1 0

PETSc blame digest (next) 2017-08-26
by PETSc checkBuilds 26 Aug '17

26 Aug '17

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/279e4bd Associated function for MatPtAP_seqaijmkl_seqmaij_C. src/mat/impls/maij/maij.c:3383 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/26/build_next_…] /sandbox/petsc/petsc.clone-4/src/mat/impls/maij/maij.c:3383:7: error: expected ';' before 'ierr' ---- warnings attributed to commit https://bitbucket.org/petsc/petsc/commits/d91d045 Merge branch 'rmills/fix-seqaijperm_seqmaij' into next src/mat/impls/maij/maij.c:3382 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/26/build_next_…] /sandbox/petsc/petsc.clone-4/src/mat/impls/maij/maij.c:3382:9: error: 'HEAD' was not declared in this scope [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/26/build_next_…] /Users/petsc/petsc.clone-4/src/mat/impls/maij/maij.c:3382:1: error: version control conflict marker in file [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/26/build_next_…] /sandbox/petsc/petsc.clone-4/src/mat/impls/maij/maij.c:3382:3: error: expected primary-expression before '<<' token [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/26/build_next_…] /sandbox/petsc/petsc.clone-4/src/mat/impls/maij/maij.c:3382:7: error: expected primary-expression before '<' token [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/26/build_next_…] /sandbox/petsc/petsc.clone-4/src/mat/impls/maij/maij.c:3382:5: error: expected primary-expression before '<<' token [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/26/build_next_…] /sandbox/petsc/petsc.clone-4/src/mat/impls/maij/maij.c:3382:1: error: expected primary-expression before '<<' token [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/26/build_next_…] /sandbox/petsc/petsc.clone-4/src/mat/impls/maij/maij.c:3382:1: error: expected expression before '<<' token src/mat/impls/maij/maij.c:3384 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/26/build_next_…] /sandbox/petsc/petsc.clone-4/src/mat/impls/maij/maij.c:3384:1: error: expected primary-expression before '==' token [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/26/build_next_…] /sandbox/petsc/petsc.clone-4/src/mat/impls/maij/maij.c:3384:1: error: expected expression before '==' token [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/26/build_next_…] /sandbox/petsc/petsc.clone-4/src/mat/impls/maij/maij.c:3384:5: error: expected primary-expression before '==' token [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/26/build_next_…] /sandbox/petsc/petsc.clone-4/src/mat/impls/maij/maij.c:3384:3: error: expected primary-expression before '==' token [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/26/build_next_…] /sandbox/petsc/petsc.clone-4/src/mat/impls/maij/maij.c:3384:7: error: expected primary-expression before '=' token src/mat/impls/maij/maij.c:3386 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/26/build_next_…] /sandbox/petsc/petsc.clone-4/src/mat/impls/maij/maij.c:3386:5: error: expected primary-expression before '>>' token [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/26/build_next_…] /sandbox/petsc/petsc.clone-4/src/mat/impls/maij/maij.c:3386:1: error: expected primary-expression before '>>' token [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/26/build_next_…] /sandbox/petsc/petsc.clone-4/src/mat/impls/maij/maij.c:3386:3: error: expected primary-expression before '>>' token [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/26/build_next_…] /sandbox/petsc/petsc.clone-4/src/mat/impls/maij/maij.c:3386:7: error: expected primary-expression before '>' token [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/26/build_next_…] /sandbox/petsc/petsc.clone-4/src/mat/impls/maij/maij.c:3386:16: error: 'fix' was not declared in this scope [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/26/build_next_…] /sandbox/petsc/petsc.clone-4/src/mat/impls/maij/maij.c:3386:9: error: 'rmills' was not declared in this scope [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/26/build_next_…] /sandbox/petsc/petsc.clone-4/src/mat/impls/maij/maij.c:3386:1: error: expected expression before '>>' token [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/26/build_next_…] /sandbox/petsc/petsc.clone-4/src/mat/impls/maij/maij.c:3386:20: error: 'seqaijperm_seqmaij' 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 (maint) 2017-08-19
by PETSc checkBuilds 19 Aug '17

19 Aug '17

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/c888390 Add MatNestSetSubMats and make MatNest creation go through MatCreate_Nest src/mat/impls/nest/matnest.c:1115 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/19/build_maint…] /sandbox/petsc/petsc.clone-3/src/mat/impls/nest/matnest.c:1115:9: warning: '*' in boolean context, suggest '&&' instead [-Wint-in-bool-context] ---- warnings attributed to commit https://bitbucket.org/petsc/petsc/commits/df0c820 DMCompositeGather now takes a single InsertMode parameter src/dm/impls/composite/pack.c:537 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/19/build_maint…] /sandbox/petsc/petsc.clone-2/src/dm/impls/composite/pack.c:537:17: warning: passing an object that undergoes default argument promotion to 'va_start' has undefined behavior [-Wvarargs] ---- To opt-out from receiving these messages - send a request to petsc-dev(a)mcs.anl.gov.

1 0

PETSc blame digest (next) 2017-08-12
by PETSc checkBuilds 12 Aug '17

12 Aug '17

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/aab5bcd Fix various compiler warnings and add PetscFunctionBegin src/dm/impls/plex/plex.c:214 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/12/build_next_…] "/export/home/petsc/petsc.clone-2/src/dm/impls/plex/plex.c", line 214: warning: syntax error: empty initializer [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/12/build_next_…] "/export/home/petsc/petsc.clone/src/dm/impls/plex/plex.c", line 214: warning: syntax error: empty initializer [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/12/build_next_…] /sandbox/petsc/petsc.clone-2/src/dm/impls/plex/plex.c:214:44: warning: ISO C forbids empty initializer braces [-Wpedantic] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/12/build_next_…] "/export/home/petsc/petsc.clone-3/src/dm/impls/plex/plex.c", line 214: warning: syntax error: empty initializer src/dm/impls/plex/plexgeometry.c:639 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/12/build_next_…] "/export/home/petsc/petsc.clone-2/src/dm/impls/plex/plexgeometry.c", line 639: warning: syntax error: empty initializer [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/12/build_next_…] "/export/home/petsc/petsc.clone-3/src/dm/impls/plex/plexgeometry.c", line 639: warning: syntax error: empty initializer [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/12/build_next_…] "/export/home/petsc/petsc.clone/src/dm/impls/plex/plexgeometry.c", line 639: warning: syntax error: empty initializer [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/12/build_next_…] /sandbox/petsc/petsc.clone-2/src/dm/impls/plex/plexgeometry.c:639:34: warning: ISO C forbids empty initializer braces [-Wpedantic] src/dm/impls/plex/plexgeometry.c:708 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/12/build_next_…] "/export/home/petsc/petsc.clone-3/src/dm/impls/plex/plexgeometry.c", line 708: warning: syntax error: empty initializer [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/12/build_next_…] "/export/home/petsc/petsc.clone/src/dm/impls/plex/plexgeometry.c", line 708: warning: syntax error: empty initializer [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/12/build_next_…] /sandbox/petsc/petsc.clone-2/src/dm/impls/plex/plexgeometry.c:708:36: warning: ISO C forbids empty initializer braces [-Wpedantic] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/12/build_next_…] "/export/home/petsc/petsc.clone-2/src/dm/impls/plex/plexgeometry.c", line 708: warning: syntax error: empty initializer ---- To opt-out from receiving these messages - send a request to petsc-dev(a)mcs.anl.gov.

1 0

PETSc blame digest (next) 2017-08-03
by PETSc checkBuilds 03 Aug '17

03 Aug '17

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/aaa6c58 TS: Deprecate TSSetInitialTimeStep() src/ts/examples/tutorials/power_grid/stability_9bus/ex9busopt_fd.c:994 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/03/examples_ne…] /usr/home/balay/petsc.clone-2/src/ts/examples/tutorials/power_grid/stability_9bus/ex9busopt_fd.c:994:33: error: request for member 'max' in 'ctx->Userctx::t', which is of non-class type 'PetscReal {aka double}' ---- To opt-out from receiving these messages - send a request to petsc-dev(a)mcs.anl.gov.

1 0

PETSc blame digest (next) 2017-08-03
by PETSc checkBuilds 03 Aug '17

03 Aug '17

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/0df0451 basic portability/security testing in compiles lib/petsc/conf/rules:401 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/03/examples_ne…] /usr/home/balay/petsc.clone-2/lib/petsc/conf/rules:401: recipe for target 'ex9busopt_fd.o' failed ---- warnings attributed to commit https://bitbucket.org/petsc/petsc/commits/2492ecd bk-changeset-1.2471 lib/petsc/conf/rules:450 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/03/examples_ne…] /usr/home/balay/petsc.clone-2/lib/petsc/conf/rules:450: recipe for target 'ex9busopt_fd.PETSc' failed ---- To opt-out from receiving these messages - send a request to petsc-dev(a)mcs.anl.gov.

1 0

PETSc blame digest (next) 2017-08-02
by PETSc checkBuilds 02 Aug '17

02 Aug '17

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/5c5f594 TS: Deprecate TSGetTimeStepNumber() src/ts/interface/ts.c:3068 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/02/build_next_…] "/export/home/petsc/petsc.clone-2/src/ts/interface/ts.c", line 3068: warning: syntax error: empty declaration [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/02/build_next_…] /sandbox/petsc/petsc.clone-2/src/ts/interface/ts.c:3068:96: warning: ISO C does not allow extra ';' outside of a function [-Wpedantic] [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/02/build_next_…] "/export/home/petsc/petsc.clone-3/src/ts/interface/ts.c", line 3068: warning: syntax error: empty declaration ---- warnings attributed to commit https://bitbucket.org/petsc/petsc/commits/aaa6c58 TS: Deprecate TSSetInitialTimeStep() src/ts/examples/tutorials/ex11.c:1965 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/08/02/examples_ne…] /sandbox/petsc/petsc.clone-3/src/ts/examples/tutorials/ex11.c:1965:9: error: too many arguments to function 'TSSetTimeStep' ---- To opt-out from receiving these messages - send a request to petsc-dev(a)mcs.anl.gov.

1 0