Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 355717

Summary: testRowAccess failure in I20110823-0925 build
Product: [Eclipse Project] JDT Reporter: Michael Rennie <Michael_Rennie>
Component: DebugAssignee: 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 Flags
partial fix
none
updated patch none

Description Michael Rennie CLA 2011-08-24 11:11:40 EDT
testRowAccess	Failure	Evaluation did not complete
junit.framework.AssertionFailedError: Evaluation did not complete
at org.eclipse.jdt.debug.tests.variables.TestIntegerAccessUnboxing15$Listener.getResult(TestIntegerAccessUnboxing15.java:54)
at org.eclipse.jdt.debug.tests.variables.TestIntegerAccessUnboxing15.doAccessTest(TestIntegerAccessUnboxing15.java:77)
at org.eclipse.jdt.debug.tests.variables.TestIntegerAccessUnboxing15.testRowAccess(TestIntegerAccessUnboxing15.java:95)
at org.eclipse.jdt.debug.tests.AbstractDebugTest.runBare(AbstractDebugTest.java:1919)
at org.eclipse.jdt.debug.tests.DebugSuite$1.run(DebugSuite.java:54)
at java.lang.Thread.run(Thread.java:680)

The tests all pass locally
Comment 1 Michael Rennie CLA 2011-09-09 12:47:31 EDT
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.
Comment 2 Michael Rennie CLA 2011-09-09 12:53:28 EDT
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)
Comment 3 Dani Megert CLA 2011-09-14 04:17:04 EDT
Still planned for M2?
Comment 4 Michael Rennie CLA 2011-09-14 10:09:49 EDT
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.
Comment 5 Michael Rennie CLA 2011-09-15 09:38:31 EDT
> Still planned for M2?

No this patch is much too large to be added this close to M2. Moving to M3
Comment 6 Michael Rennie CLA 2011-09-22 13:15:42 EDT
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
Comment 7 Michael Rennie CLA 2011-10-28 10:00:27 EDT
have not seen these failures in many builds - verified