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.
[200406131800] Test Suite org.netbeans.CLIHandlerTest testServerWaitsBeforeFinishInitializationIsCalledOn: junit.framework.AssertionFailedError: H is not executed before finishInitialization is called expected:<2> but was:<1> at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.failNotEquals(Assert.java:282)
Created attachment 15689 [details] exception stacktrace
May I ask for some additional info? The first know day of failure. Intermitent or always failing? Only one platform or more of them? Just windows 2000 and no XP, etc.? Thanks.
The test fails on Win 2k. Details about platform: Host : QA-W2K-S3 Operating System Name : Windows 2000 Operating System Version : 5.0 System Architecture : x86 Java Version : 1.4.2_04 Java Vendor : Sun Microsystems Inc. User Language : en
And the failures? How often? When was the first failure?
core$ cvs -q ci -m "In order to hunt down #44833 the test has been improved to provide more useful failure info" Checking in test/unit/src/org/netbeans/CLIHandlerTest.java; /cvs/core/test/unit/src/org/netbeans/CLIHandlerTest.java,v <-- CLIHandlerTest.java new revision: 1.6; previous revision: 1.5 done
The test fails again. testServerWaitsBeforeFinishInitializationIsCalledOn: junit.framework.AssertionFailedError: H is not executed before finishInitialization is called :2 cnt: 2 at junit.framework.Assert.fail(Assert.java:47) at org.netbeans.CLIHandlerTest.testServerWaitsBeforeFinishInitializationIsCalledOn(CLIHandlerTest.java:284) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
Of course the test works for me. I have enhanced the debugging capabilities of the test and I am looking forward to get the new failure output. Until then, closing. Checking in bootstrap/src/org/netbeans/CLIHandler.java; /cvs/core/bootstrap/src/org/netbeans/CLIHandler.java,v <-- CLIHandler.java new revision: 1.13; previous revision: 1.12 done Processing log script arguments... More commits to come... Checking in test/unit/src/org/netbeans/CLIHandlerTest.java; /cvs/core/test/unit/src/org/netbeans/CLIHandlerTest.java,v <-- CLIHandlerTest.java new revision: 1.7; previous revision: 1.6
The test fails again
Created attachment 16556 [details] test log
Looks like everything is all right. The bug will likely be in test. Please sent me another log. cvs -q ci -m "Improved logging. Still trying to understand failures behind issue 44833" Checking in unit/src/org/netbeans/CLIHandlerTest.java; /cvs/core/test/unit/src/org/netbeans/CLIHandlerTest.java,v <-- CLIHandlerTest.java new revision: 1.10
Created attachment 16701 [details] another test log
another test log added ...
cvs ci -m "#44833: Making the test more robust against the thread switching semantics. Right now it really waits for both threads that can do the initialization (either the RequestProcessor or the second CLI handler) to both finish." core/test/unit/src/org/netbeans/CLIHandlerTest.java,v <-- CLIHandlerTest.java new revision: 1.11
v