On Tue, Jun 2, 2015 at 7:40 AM, Barry Smith <[email protected]> wrote:
> > > On Jun 1, 2015, at 11:38 PM, Jed Brown <[email protected]> wrote: > > > > Barry Smith <[email protected]> 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, > > > http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2015/06/01/make_master_arch-freebsd-cxx-pkgs-opt_wii.log > > perhaps the problem is with some other "script"? > Did Satish swap the builds in anticipation of a release? Matt > > > >> 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'. > > -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener
