Bug 351331 - testStepOverHitsNestedEvaluationHandlerResume test failure in I20110705-0800 build
Summary: testStepOverHitsNestedEvaluationHandlerResume test failure in I20110705-0800 ...
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.7   Edit
Hardware: Macintosh Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks: 412552
  Show dependency tree
 
Reported: 2011-07-06 09:47 EDT by Michael Rennie CLA
Modified: 2018-11-22 21:35 EST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Rennie CLA 2011-07-06 09:47:10 EDT
The failure cannot be reproduced locally, so we will have to keep an eye on it.

The failure message:

Should be in frame where step originated expected:<org.eclipse.jdt.internal.debug.core.model.JDIStackFrame@1621ccc> but was:<org.eclipse.jdt.internal.debug.core.model.JDIStackFrame@523>
junit.framework.AssertionFailedError: Should be in frame where step originated expected:<org.eclipse.jdt.internal.debug.core.model.JDIStackFrame@1621ccc> but was:<org.eclipse.jdt.internal.debug.core.model.JDIStackFrame@523>
at org.eclipse.jdt.debug.tests.breakpoints.JavaBreakpointListenerTests.testStepOverHitsNestedEvaluationHandlerResume(JavaBreakpointListenerTests.java:840)
at org.eclipse.jdt.debug.tests.AbstractDebugTest.runBare(AbstractDebugTest.java:1765)
at org.eclipse.jdt.debug.tests.DebugSuite$1.run(DebugSuite.java:54)
at java.lang.Thread.run(Thread.java:680)
Comment 1 Eclipse Genie CLA 2018-11-22 15:30:14 EST
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.

If you have further information on the current state of the bug, please add it. 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.
Comment 2 Sarika Sinha CLA 2018-11-22 21:35:39 EST
Not seen this failing so closing it as of now.