On Mon, Nov 12, 2012 at 08:56:10AM -0800, Roland Haas wrote:
Next release:
- query on cactususers for suggestions for next release goal
We also talked about trying to look into the number of compiler warnings that are generated. I produced a graph showing the status as of the last release [1], parsed from the output of a build [2]. Most of the warnings are produced from auto-generated code, for shadowed and/or unused variables; and Ian Hinder has some ideas about how to fix this. Others will have to be looked into by hand.
I will setup a cron job updating this graph every night and announce once that is setup and working.
In principle this should be an easy addition to any already present automated build (just build with -Wall, capture the build logs and run two scripts to generate that plot). However, the current script is likely to get confused if the build is done in parallel and thus the log is all mixed up, so I build in serial for this for now. I opened a ticket (https://trac.einsteintoolkit.org/ticket/1180) to collect ideas how to deal with that.
Frank
The following links are _not_ persistent.
[1] http://www.cct.lsu.edu/~knarf/ET_stats/warnings.png [2] http://www.cct.lsu.edu/~knarf/ET_stats/build.log ( 39MB )