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.
The way how we measure test speed of various algorithms is fragile with respect to GC and hotspot compiler interruptions. Sometimes the tests are failing even the general algorithm is ok. One possible idea would be to re-run the test if it fails once. This however needs enhancements in the suite that compares all the test results. Also it was suggested by tball that the suite could specify the complexity of algoritm and then just compare the expected state with reality. Might be useful to handle this as well during fixing the repeated execution problem.
Currently broken test is org.openide.loaders.DataShadowBrokenSlownessTest
cvs -q ci -m "52486: NbTestSuite enhanced with method speedSuite to allow more reliable implementation of speed comparation tests. DataShadow* tests rewritten to use it." openide xtest Checking in openide/test/unit/src/org/openide/loaders/DataShadowBrokenSlownessTest.java; /cvs/openide/test/unit/src/org/openide/loaders/DataShadowBrokenSlownessTest.java,v <-- DataShadowBrokenSlownessTest.java new revision: 1.4; previous revision: 1.3 done Checking in openide/test/unit/src/org/openide/loaders/DataShadowSlowness39981Test.java; /cvs/openide/test/unit/src/org/openide/loaders/DataShadowSlowness39981Test.java,v <-- DataShadowSlowness39981Test.java new revision: 1.5; previous revision: 1.4 done Processing log script arguments... More commits to come... Checking in xtest/nbjunit/src/org/netbeans/junit/NbTestCase.java; /cvs/xtest/nbjunit/src/org/netbeans/junit/NbTestCase.java,v <-- NbTestCase.java new revision: 1.26; previous revision: 1.25 done Checking in xtest/nbjunit/src/org/netbeans/junit/NbTestSuite.java; /cvs/xtest/nbjunit/src/org/netbeans/junit/NbTestSuite.java,v <-- NbTestSuite.java new revision: 1.5; previous revision: 1.4
Verified.