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 231245 - org.openide.nodes.ChildrenArrayNodeAtShouldNotBeSlowTest failures
Summary: org.openide.nodes.ChildrenArrayNodeAtShouldNotBeSlowTest failures
Status: RESOLVED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Nodes (show other bugs)
Version: 7.4
Hardware: PC Linux
: P1 normal (vote)
Assignee: Jan Peska
URL: http://deadlock.netbeans.org/hudson/j...
Keywords: TEST
Depends on:
Blocks:
 
Reported: 2013-06-13 23:24 UTC by Martin Entlicher
Modified: 2013-06-19 13:39 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 Martin Entlicher 2013-06-13 23:24:42 UTC 
Some tests fail like:

org.openide.nodes.ChildrenArrayNodeAtShouldNotBeSlowTest.test1245
junit.framework.AssertionFailedError: Too big differences when various number of shadows is used:
Test 140 took 116 ms
Test 599 took 1673 ms
Test 1245 took 84 ms
Test 10 took 22 ms

	at org.openide.nodes.ChildrenArrayNodeAtShouldNotBeSlowTest.assertNumbersAreSane(ChildrenArrayNodeAtShouldNotBeSlowTest.java:186)
	at org.openide.nodes.ChildrenArrayNodeAtShouldNotBeSlowTest.tearDown(ChildrenArrayNodeAtShouldNotBeSlowTest.java:114)
	at org.netbeans.junit.NbTestCase.runBare(NbTestCase.java:471)
	at org.netbeans.junit.NbTestCase.run(NbTestCase.java:288)


or
org.openide.nodes.ChildrenArrayNodeAtShouldNotBeSlowTest.test10746
junit.framework.AssertionFailedError: Too big differences when various number of shadows is used:
Test 10746 took 16 ms
Test 3553 took 16 ms
Test 140 took 116 ms
Test 599 took 1673 ms
Test 1245 took 84 ms
Test 10 took 22 ms

	at org.openide.nodes.ChildrenArrayNodeAtShouldNotBeSlowTest.assertNumbersAreSane(ChildrenArrayNodeAtShouldNotBeSlowTest.java:186)
	at org.openide.nodes.ChildrenArrayNodeAtShouldNotBeSlowTest.tearDown(ChildrenArrayNodeAtShouldNotBeSlowTest.java:114)
	at org.netbeans.junit.NbTestCase.runBare(NbTestCase.java:471)
	at org.netbeans.junit.NbTestCase.run(NbTestCase.java:288)

See http://deadlock.netbeans.org/hudson/job/NB-Core-Build/10347/testReport/
http://deadlock.netbeans.org/hudson/job/NB-Core-Build/10348/testReport/
Comment 1 Martin Entlicher 2013-06-18 12:55:39 UTC 
Instead of measuring wall time, you may consider measuring CPU time:
http://nadeausoftware.com/articles/2008/03/java_tip_how_get_cpu_and_user_time_benchmarking
Comment 2 Jan Peska 2013-06-19 13:39:41 UTC 
After a offline discussion with Jarda Tulach - writer of the test. I've decided to mark it as RF again. According to Jarda this test was useful right after he changed a list implementation representing node children and that was more then 5 years ago -> Fixed by marking the test as RF