New build questions

[Jonathan Gibbons]

On 10/17/2011 01:34 PM, Fredrik Öhrström wrote:
>> Could the new build report the number of warnings that occurred during the
>> >  build? Simply "grep-ing" for the word "warning" (ignoring case) is usually a
>> >  pretty good measure.
> How would you handle that different C++ compilers give different warnings?

As I suggested, something like "grep -i -w warning" is a good indicator.
In the work I've done in the past to analyze warnings, this has picked
up most warnings. Do you have examples where this picks up lines
it should not, or misses lines that it should?

> For the moment I have disabled as many javac warnings as possible.
> When we assign 200 programmers to fix all the warnings in a month,
> they can enable a single warning and go through that first. Then enable
> the next warning.
>
> If we enable all warnings right now, then the number of warnings
> will be overwhelming. They already are for the ones that cannot
> be turned off.
>
> Thus the number of warnings will fluctuate a lot. Perhaps we can
> do this when everything has stabilized quite a lot.

This past summer, an intern named Sasha Boulgakov made great
progress on reducing the number of javac warnings in the JDK 8 forest.

I understand your desire to reduce the visual clutter as much as possible,
especially when developers are running the build directly. But, I think 
it is also
important not to brush the warnings under the carpet.  It should be possible
to enable and monitor the warnings, in systems like nightly build or 
other CI
environments.

-- Jon