Comment 1 Dani Megert 2013-07-25 04:20:11 EDT

Created attachment 233783 [details]
Test result

Comment 2 Michael Rennie 2013-07-29 16:49:59 EDT

Pushed fix to: http://git.eclipse.org/c/jdt/eclipse.jdt.debug.git/commit/?id=aa1994b1175aa087d820a3d3958da63fbbf381bb

By removing the job from the workspace revert and having the setup wait for a build to complete, we should avoid not finding the types. I also added an assert to check for null-ness of the IType we are trying to set a breakpoint on.

This fix will likely also fix bug 413605.

Comment 3 Dani Megert 2013-07-30 04:27:57 EDT

Worked in N20130729-2000.

Comment 4 Michael Rennie 2013-07-30 09:30:25 EDT

Thanks for verifying Dani, I will mark this one fixed, but leave bug 413605 open for a few more builds just to be sure.

Comment 5 Dani Megert 2013-08-15 03:33:04 EDT

Please cherry-pick the fix into 'R4_3_maintenance' as we got the failures in the last M-build too: http://download.eclipse.org/eclipse/downloads/drops4/M20130814-0800/testresults/html/org.eclipse.jdt.debug.tests_win32.win32.x86_7.0.html

Comment 6 Michael Rennie 2013-08-19 11:11:44 EDT

done: http://git.eclipse.org/c/jdt/eclipse.jdt.debug.git/commit/?h=R4_3_maintenance&id=2b24565ad8f005ded1962338ea3516b2655a0973

Comment 7 Sarika Sinha 2017-06-09 00:49:37 EDT

Failed
http://download.eclipse.org/eclipse/downloads/drops4/I20170608-0530/testresults/html/org.eclipse.jdt.debug.tests_ep47I-unit-win32_win32.win32.x86_8.0.html

testClassLoadBreakPoint	Failure	type not specified for class prepare breakpoint

junit.framework.AssertionFailedError: type not specified for class prepare breakpoint
at org.eclipse.jdt.debug.tests.AbstractDebugTest.createClassPrepareBreakpoint(AbstractDebugTest.java:1918)
at org.eclipse.jdt.debug.tests.AbstractDebugTest.createClassPrepareBreakpoint(AbstractDebugTest.java:1880)
at org.eclipse.jdt.debug.tests.refactoring.MoveCompilationUnitTests.testClassLoadBreakPoint(MoveCompilationUnitTests.java:146)
at org.eclipse.jdt.debug.tests.AbstractDebugTest.runBare(AbstractDebugTest.java:2528)
at org.eclipse.jdt.debug.tests.DebugSuite$1.run(DebugSuite.java:57)
at java.lang.Thread.run(Thread.java:745)
	1.036
testLineBreakPoint	Failure	Could not find the requested IType: a.b.c.Movee

junit.framework.AssertionFailedError: Could not find the requested IType: a.b.c.Movee
at org.eclipse.jdt.debug.tests.AbstractDebugTest.createLineBreakpoint(AbstractDebugTest.java:1546)
at org.eclipse.jdt.debug.tests.refactoring.MoveCompilationUnitTests.testLineBreakPoint(MoveCompilationUnitTests.java:71)
at org.eclipse.jdt.debug.tests.AbstractDebugTest.runBare(AbstractDebugTest.java:2528)
at org.eclipse.jdt.debug.tests.DebugSuite$1.run(DebugSuite.java:57)
at java.lang.Thread.run(Thread.java:745)
	0.314
testMethodBreakPoint	Failure	wrong type name expected:<a.b.[]Movee> but was:<a.b.[c.]Movee>

junit.framework.ComparisonFailure: wrong type name expected:<a.b.[]Movee> but was:<a.b.[c.]Movee>
at org.eclipse.jdt.debug.tests.refactoring.MoveCompilationUnitTests.testMethodBreakPoint(MoveCompilationUnitTests.java:102)
at org.eclipse.jdt.debug.tests.AbstractDebugTest.runBare(AbstractDebugTest.java:2528)
at org.eclipse.jdt.debug.tests.DebugSuite$1.run(DebugSuite.java:57)
at java.lang.Thread.run(Thread.java:745)

Comment 8 Eclipse Genie 2020-05-20 11:59:30 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.