| Summary: | testRowAccess failure in I20110823-0925 build | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Michael Rennie <Michael_Rennie> | ||||||
| Component: | Debug | Assignee: | Michael Rennie <Michael_Rennie> | ||||||
| Status: | VERIFIED FIXED | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | daniel_megert | ||||||
| Version: | 3.6 | ||||||||
| Target Milestone: | 3.8 M3 | ||||||||
| Hardware: | Macintosh | ||||||||
| OS: | Mac OS X | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
|
Description
Michael Rennie
Created attachment 203075 [details]
partial fix
The mentioned tests and another group of related the tests no longer pass locally because it appears there is a problem with the class files. This patch changes the way the test set up the test projects to ensure they have the correct compliance, but I am still getting some weird failures locally.
Here is the trace I am getting: !MESSAGE Test case: testStaticTypeParameter Never received event: Suspend Process exit value: 1 Console output follows: Exception in thread "main" java.lang.UnsupportedClassVersionError: Bad version number in .class file at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:676) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) at java.net.URLClassLoader.access$100(URLClassLoader.java:56) at java.net.URLClassLoader$1.run(URLClassLoader.java:195) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:317) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:280) at java.lang.ClassLoader.loadClass(ClassLoader.java:252) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:375) Still planned for M2? Created attachment 203337 [details]
updated patch
This patch includes a much needed over-haul to the debug tests and completely removes the use of our ProjectCreationDecorator to create test projects - so now each test can be run on its own.
> Still planned for M2?
No this patch is much too large to be added this close to M2. Moving to M3
Made a few updates to the other patch around testing again (using our TestAgainException mechanism) for tests that randomly fail. Pushed fix to MASTER - http://git.eclipse.org/c/jdt/eclipse.jdt.debug.git/commit/?id=41abce05f2dd552059d60fa1b4bf7970c4a30f77 have not seen these failures in many builds - verified |