[vtk-developers] Defects in recent checkins

[Bill Lorensen]

Bob,

A recent commit has introduced some defects:

1) http://www.cdash.org/CDash/testDetails.php?test=126570163&build=1812089
File: /home/kitware/Dashboards/MyTests/VTK/IO/vtkLSDynaPartCollection.h
has 2 includes:
   16: #include "LSDynaMetaData.h"
   18: #include "vtkObject.h"
File: /home/kitware/Dashboards/MyTests/VTK/IO/vtkLSDynaPart.h does not
define copy constructor
Should be:
vtkLSDynaPart(const vtkLSDynaPart&); // Not implemented
File: /home/kitware/Dashboards/MyTests/VTK/IO/vtkLSDynaPart.h does not
define assignment operator
Should be:
void operator=(const vtkLSDynaPart&); // Not implemented

2) Lots of visual studio warnings
http://www.cdash.org/CDash/viewBuildError.php?type=1&buildid=1812759
gcc warnings http://www.cdash.org/CDash/viewBuildError.php?type=1&buildid=1805740
mac warnings http://www.cdash.org/CDash/viewBuildError.php?type=1&buildid=1805998

3) A valgrind defect
http://www.cdash.org/CDash/viewDynamicAnalysisFile.php?id=2569504

4) PrintSelf defects
http://www.cdash.org/CDash/testDetails.php?test=126565133&build=1812183
http://www.cdash.org/CDash/testDetails.php?test=126565543&build=1812183

5) Failing tests
http://www.cdash.org/CDash/viewTest.php?onlydelta&buildid=1805773


I find that the best way to detect new defects is to look at the
dashboard the day after your checkins:
http://www.cdash.org/CDash/index.php?project=VTK&date=2011-12-10

Then look at each + on warnings, errors, and tests to see if the
recent code may have introduced the defects. And check the valgrind at
the end of the dashboard

Thanks,

Bill
-- 
Unpaid intern in BillsBasement at noware dot com