On Sun, Mar 22, 2015 at 01:04:39PM -0500, Barry Smith wrote: > > > On Mar 22, 2015, at 9:00 AM, checkBuilds <[email protected]> wrote: > > > > > > > > Dear PETSc developer, > > > > This email contains listings of contributions attributed to you by > > `git blame` that caused compiler errors or warnings in PETSc nightly > > build testing. Warnings are labeled by the machine, PETSC_ARCH, and > > git branch that generated the warnings. These warnings may be > > missing some context: for the full context, please go to the nightly > > build website [1] and find the corresponding log file: either > > build_(branch)_(PETSC_ARCH)_(machine).log, or > > examples_(branch)_(PETSC_ARCH)_(machine).log. > > Hmm, we need to fix this. No way is it right that people have to figure > out the name of the log file when software should be generating the exact > link directly for people. How hard is it to add this ?
I'll look into it. Toby > > Barry > > > > > Thanks, > > The PETSc development team > > > > [1] http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2015/03/22 > > > > --- > > > > warnings attributed to commit ceba6b7 Sys: Have to check for all zero sizes > > in PetscMalloc*() > > > > include/petscsys.h:667 > > [crank,arch-linux-pkgs-opt,next] > > /sandbox/petsc/petsc.clone/include/petscsys.h:667:76: warning: 'perm' may > > be used uninitialized in this function [-Wmaybe-uninitialized] > > [cg,arch-linux-opt-cxx-quad,next] > > /sandbox/petsc/petsc.clone/include/petscsys.h:667:76: warning: 'perm' may > > be used uninitialized in this function [-Wmaybe-uninitialized] > > >
signature.asc
Description: Digital signature
