[petsc-dev] [petsc-checkbuilds] PETSc blame digest (master) 2015-06-01

Barry Smith bsmith at mcs.anl.gov
Tue Jun 2 07:40:53 CDT 2015

> On Jun 1, 2015, at 11:38 PM, Jed Brown <jed at jedbrown.org> wrote:
> Barry Smith <bsmith at mcs.anl.gov> writes:
>>  Jed,
>>   What the fuck is this doing in master? 
> It is not in 'master'.
> $ git branch -r --contains 4b4eb8d
>  bb/jed/mat-assembly-perf
>  bb/next
> Is something wrong with the script?

   Well the problem is not with the "script" that pulls out the warnings/errors since the "master" log files also contain the warnings, for example,


perhaps the problem is with some other "script"?

>>   It has sent email for weeks and weeks from next with this exact
>>   warning message and should never have been moved over to master
>>   until the error was fixed.  It is inexcusable that this problem got
>>   moved into master after it was broken so long in next and never
>>   fixed.
> As far as I can tell, these are only warnings and only appear with C++
> when using some particular compiler versions.  I figured that was an
> excuse for "not urgent", but I realize it's been entirely too long.  I
> found a compiler that could reproduce the warning and have fixed it in
> 'next'.

More information about the petsc-dev mailing list