Dave,
It is only a "guess" at who is blame for a particular fault. It could
easily be a different commit or different person who introduced the fault.
In this case you can just ignore it.
Barry
> On Apr 7, 2016, at 4:50 PM, Dave May <[email protected]> wrote:
>
> I don't fully understand this report.
>
> Commits related to PCSemiRedundant involved a file called sred_dmda.c, yet
> the warning is associated with telescope_dmda.c
>
> Does the report imply that code generating these warnings was always present
> from the initial commit. Given the filename changed and a lot of things were
> altered in this file (now called telescope_dmda.c) I'm surprised that the
> warning can be traced all the way back to the first commit.
>
>
>
> On 7 April 2016 at 16:00, PETSc 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 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/36501ec
> PCSemiRedundant:
>
> src/ksp/pc/impls/telescope/telescope_dmda.c:1001
>
> [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2016/04/07/build_next_arch-linux-analyzer_crush.log]
>
> /sandbox/petsc/petsc.clone/src/ksp/pc/impls/telescope/telescope_dmda.c:1001:12:
> warning: Function call argument is an uninitialized value
>
> src/ksp/pc/impls/telescope/telescope_dmda.c:154
>
> [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2016/04/07/build_next_arch-linux-analyzer_crush.log]
>
> /sandbox/petsc/petsc.clone/src/ksp/pc/impls/telescope/telescope_dmda.c:154:11:
> warning: Assigned value is garbage or undefined
>
> ----
>
> warnings attributed to commit
> https://bitbucket.org/petsc/petsc/commits/6ab51f8
> PCSemiRedundant:
>
> src/ksp/pc/impls/telescope/telescope.c:193
>
> [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2016/04/07/build_next_arch-linux-analyzer_crush.log]
>
> /sandbox/petsc/petsc.clone/src/ksp/pc/impls/telescope/telescope.c:193:9:
> warning: Dereference of undefined pointer value
>
> src/ksp/pc/impls/telescope/telescope.c:206
>
> [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2016/04/07/build_next_arch-linux-analyzer_crush.log]
>
> /sandbox/petsc/petsc.clone/src/ksp/pc/impls/telescope/telescope.c:206:12:
> warning: Function call argument is an uninitialized value
>
> src/ksp/pc/impls/telescope/telescope_dmda.c:254
>
> [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2016/04/07/build_next_arch-linux-analyzer_crush.log]
>
> /sandbox/petsc/petsc.clone/src/ksp/pc/impls/telescope/telescope_dmda.c:254:11:
> warning: Assigned value is garbage or undefined
>
> src/ksp/pc/impls/telescope/telescope_dmda.c:854
>
> [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2016/04/07/build_next_arch-linux-analyzer_crush.log]
>
> /sandbox/petsc/petsc.clone/src/ksp/pc/impls/telescope/telescope_dmda.c:854:9:
> warning: Dereference of undefined pointer value
>
> ----
>
> warnings attributed to commit
> https://bitbucket.org/petsc/petsc/commits/f650675
> PCTelescope:
>
> src/ksp/pc/impls/telescope/telescope_dmda.c:867
>
> [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2016/04/07/build_next_arch-linux-analyzer_crush.log]
>
> /sandbox/petsc/petsc.clone/src/ksp/pc/impls/telescope/telescope_dmda.c:867:12:
> warning: Function call argument is an uninitialized value
>
> ----
> To opt-out from receiving these messages - send a request to
> [email protected].
>
