[cdt-dev] Failed Sanity for CDT build 200403290300 (M8 candidate)

[Mathieu Lapensee <lapensee@xxxxxxxxxx>]

Recommendation:    
Build not
recommended to be adopted.  

Results:

	Windows 2.0.0.200403290300  (Sun JRE 1.4.2)	Linux 2.0.0.200403290300 (Sun JRE 1.4.2)
0	698 tests, 3 failures  56566: 3 JUnit tests fails for build 2.0.0.200403290300	(new) 56571: we could not install CDT using the Update Manager (more investigation is needed) 698 tests, 3 failures  56566: 3 JUnit tests fails for build 2.0.0.200403290300
1	Pass	Pass
2	Pass	Pass
3	Pass	Pass
4	Pass	Pass
5	Pass	Pass
6	Pass	Pass
7	(new)  Blocker (56567: C/C++ Search not working (compilation problem)	(new) Blocker (56567: C/C++ Search not working (compilation problem)
8	(existing issue) 54836: Debug blue source pointer now showing when stepping through code... (existing issue) 50221: Editor marker bar does not display new breakpoints	(existing issue) 54836: Debug blue source pointer now showing when stepping through code... (existing issue) 50221: Editor marker bar does not display new breakpoints
9	(existing issue) 54842: 3 CDT nested exceptions after shutting down Eclipse (existing issue) 55149: ScannerConfig messages in log file (new) 56582: [Search] 2 Exceptions in the .log file (new) 56583: [Make Target] 2 Exceptions in the .log file (new) 56584: [Core] Exception in the .log file	(existing issue) 54842: 3 CDT nested exceptions after shutting down Eclipse (existing issue) 55149: ScannerConfig messages in log file

Notes: 
None at this time

Sanity testing assumes your environment is set up with:
a. Sun JDK 1.4.2_02 on your path ("java -version") 
b. g++, nm, c++filt is on your path 
c. "gdb -version" = 5.2.1, 5.3, or 6.0
d. You run Eclipse 3.0.0.200403261517 (M8 build) (with or without the -data
argument) 
e. Use Install/Update Perspective to get to http://update.eclipse.org/tools/cdt/updates/builds/2.0

Sanity Tests:
0.  JUnit Test Results
1.  Creating new standard/managed C/C++ projects
2.  Import existing projects. 
3.  Automatic building of a project. 
4.  Building a managed make project. 
5.  Building a standard make project.
6.  Files are parsed for language highlighting, and for Outline View.
7.  C/C++ search from the Search dialog. 
8.  You can create and run debug configurations. 
9.  Close the session and look for silent failures captured in the
.metadata/.log file. 

Cheers,

Mathieu Lapensée
CDT Software Verification Lead
IBM - SWG - Rational Division
(613) 599-3933
email: lapensee@xxxxxxxxxx