From: Peter V. <pet...@ya...> - 2006-07-01 11:01:18
|
The dashboard is currently facing the problem that only warnings from v3p/netlib & v3p/tif are visible, while we are more interested in subsequent ones! E.g., on the FreeBSD-6.1_gcc-4.1.0 build, the last line of the "Warnings" screen says: File: v3p/tiff/tif_dirread.c Line: 87 /.../vxl_src/v3p/tiff/tif_dirread.c:87: warning: 'dv' may be used uninitialized in this function The maximum number of reported warnings or errors has been reached!!! Apparently most other dashboard builds have this limit of 50 warnings. Which of the following "solutions" would be most appropriate? - correct all those warnings in v3p, making it less "standard", i.e., less 3rd party. - switch off warnings in v3p (either through some CMake functionality, or through Dart? Or in the source code? Problem: compiler & platform specific switches?) - remove the limit of 50 warnings; problem: again, compiler specific? second problem: storage & communication overhead for Dart; third problem: more difficult to immediately spot "real" problems in vxl/core - Add a column to the Dashboard with just the vxl/core warnings? - ... ? Any comments? Suggestions? -- Peter. |
From: Brad K. <bra...@ki...> - 2006-07-02 16:13:53
|
Peter Vanroose wrote: > The dashboard is currently facing the problem that only warnings from v3p/netlib & v3p/tif are > visible, while we are more interested in subsequent ones! > > E.g., on the FreeBSD-6.1_gcc-4.1.0 build, the last line of the "Warnings" screen says: > > File: v3p/tiff/tif_dirread.c Line: 87 > /.../vxl_src/v3p/tiff/tif_dirread.c:87: warning: 'dv' may be used uninitialized in this function > The maximum number of reported warnings or errors has been reached!!! > > Apparently most other dashboard builds have this limit of 50 warnings. > Which of the following "solutions" would be most appropriate? > > - correct all those warnings in v3p, making it less "standard", i.e., less 3rd party. > - switch off warnings in v3p (either through some CMake functionality, or through Dart? Or in the > source code? Problem: compiler & platform specific switches?) > - remove the limit of 50 warnings; problem: again, compiler specific? second problem: storage & > communication overhead for Dart; third problem: more difficult to immediately spot "real" problems > in vxl/core > - Add a column to the Dashboard with just the vxl/core warnings? The warnings are due to my netlib changes. They are all in f2c-generated code which is not really 3rd party. I'm planning to correct the code and/or disable warnings in the v3p/netlib directory. The 50-warning limit was added to ctest to avoid huge disk space requirements on the Dart server. The idea is that when code is maintained well enough to keep the warnings at zero normally, new warnings will appear in the first 50. I've just been slow to fix the new netlib warnings, for which I apologize. -Brad |