Bug 569992

Summary: Junit 3 execution time computed wrong
Product: [Eclipse Project] JDT Reporter: Carsten Hammer <carsten.hammer>
Component: UIAssignee: JDT-UI-Inbox <jdt-ui-inbox>
Status: NEW --- QA Contact:
Severity: minor    
Priority: P3    
Version: 4.19   
Target Milestone: ---   
Hardware: PC   
OS: Windows 10   
See Also: https://bugs.eclipse.org/bugs/show_bug.cgi?id=566379
Whiteboard: stalebug

Description Carsten Hammer CLA 2020-12-31 04:55:31 EST
Try the following snippet (plain junit 3 based test):

import junit.framework.TestCase;

public class Asdf extends TestCase {


	public void testTimer() {
		long starttime= System.currentTimeMillis();
		try {
			Thread.sleep(2000);
		} catch (InterruptedException e) {
			// TODO Auto-generated catch block
			e.printStackTrace();
		}

		assertTrue((System.currentTimeMillis()-starttime)>2000);

	}
}


Running it using a run configuration for junit 3 sometimes shows execution time below 2000 milliseconds what is always wrong. Junit 4 sometimes shows exactly 2000 milliseconds and Junit 5 shows always more than 2000 milliseconds what seems to be OK.
Comment 1 Eclipse Genie CLA 2023-01-06 18:24:01 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.