This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 54442 - some tests failing
Summary: some tests failing
Status: CLOSED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Output Window (show other bugs)
Version: 4.x
Hardware: All All
: P2 blocker (vote)
Assignee: Milos Kleint
URL:
Keywords: TEST
Depends on:
Blocks:
 
Reported: 2005-02-03 09:10 UTC by Milos Kleint
Modified: 2008-12-22 21:48 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
failure from 2005-10-31 16:54:05.967 (8.50 KB, text/html)
2005-11-02 16:45 UTC, Jaroslav Tulach 		Details
Dec 21, 2005 failure, please evaluate and possibly remove from release50 branch (6.67 KB, text/html)
2005-12-21 15:54 UTC, Jaroslav Tulach 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Milos Kleint 2005-02-03 09:10:54 UTC 
org.netbeans.core.output2. OutWriterTest  	 
testAddChangeListener   	    	   	 200501271900
org.netbeans.core.output2. OutputDocumentTest 
testDocumentEventSimilarity 	  		200502012121
org.netbeans.core.output2. OutputWindowTest 
testScrollToEnd 	  		200502021900
Comment 1 Jaroslav Tulach 2005-11-02 16:44:37 UTC 
tests continue to fail please evaluate
Comment 2 Jaroslav Tulach 2005-11-02 16:45:35 UTC 
Created attachment 26578 [details]
failure from  2005-10-31 16:54:05.967
Comment 3 Milos Kleint 2005-12-05 14:00:14 UTC 
some test failures fixed, the rest is non reproducible. Will address when they
appear again or delete them as some are non deterministic in nature.
Comment 4 Jaroslav Tulach 2005-12-21 15:52:50 UTC 
New failure.
Comment 5 Jaroslav Tulach 2005-12-21 15:54:30 UTC 
Created attachment 28015 [details]
Dec 21, 2005 failure, please evaluate and possibly remove from release50 branch
Comment 6 Milos Kleint 2005-12-22 08:58:45 UTC 
the test is random in nature, it's just sleeping ofr a certain amount of time
expecting something to happen on a second thread. That's non deterministic and
not a real unit test IMHO. 

Caret position should be at the end (end: 260, carretPos: 247) expected:<260>
but was:<247>
the difference is exactly one line of output.

I removed the test both from trunk and release50 branch.
Comment 7 Jaromir Uhrik 2006-01-16 15:44:36 UTC 
Marking this issue as VERIFIED since the issue reporter == issue owner.