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

Bug 357488

Summary: "Program did not suspend" test failures
Product: [Eclipse Project] JDT Reporter: Michael Rennie <Michael_Rennie>
Component: DebugAssignee: JDT-Debug-Inbox <jdt-debug-inbox>
Status: NEW --- QA Contact:
Severity: normal    
Priority: P3    
Version: 3.6   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard: stalebug
Bug Depends on:    
Bug Blocks: 412552    

Description Michael Rennie CLA 2011-09-13 09:43:18 EDT 
Reported from the I20110912-2126 test failures - but happening prior to that build.

Every now and again we get test failures about the program not suspending. We should investigate these failures to see if we can make the tests more stable.

Program did not suspend.
junit.framework.AssertionFailedError: Program did not suspend.
at org.eclipse.jdt.debug.tests.AbstractDebugTest.evaluate(AbstractDebugTest.java:1585)
at org.eclipse.jdt.debug.tests.core.LocalVariableTests.testEvaluationAssignments(LocalVariableTests.java:90)
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)
Comment 1 Michael Rennie CLA 2011-12-15 11:04:33 EST 
failed again in the M20111214-1406 build
Comment 2 Eclipse Genie CLA 2020-07-14 17:44:51 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.

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 3 Eclipse Genie CLA 2022-08-26 09:22:00 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.

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.