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.
When this exception occurs, it seems to be positively correlated with the next junit testcase "stalling" the test process (which hangs indefinitely with essentially zero CPU utilization). This exception is not thrown, and the "stalling" does not happen in NB 6.1, when running the same test in the same project. Build: NetBeans IDE 6.5 Beta (Build 200808111757) VM: Java HotSpot(TM) Client VM, 1.5.0_13-119, Java(TM) 2 Runtime Environment, Standard Edition, 1.5.0_13-b05-237 OS: Mac OS X, 10.5.4, i386 User comments: running junit tests STACKTRACE: (first 10 lines) java.lang.AssertionError at org.netbeans.modules.junit.output.JUnitOutputReader.messageLogged(JUnitOutputReader.java:407) at org.netbeans.modules.junit.output.JUnitAntLogger.messageLogged(JUnitAntLogger.java:276) at org.apache.tools.ant.module.bridge.impl.NbBuildLogger.messageLogged(NbBuildLogger.java:599) at org.apache.tools.ant.Project.fireMessageLoggedEvent(Project.java:2171) at org.apache.tools.ant.Project.fireMessageLogged(Project.java:2271) at org.apache.tools.ant.Project.log(Project.java:449) at org.apache.tools.ant.Task.log(Task.java:294) at org.apache.tools.ant.taskdefs.LogOutputStream.processLine(LogOutputStream.java:90) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask$JUnitLogOutputStream.processLine(JUnitTask.java:1771) at org.apache.tools.ant.taskdefs.LogOutputStream.processLine(LogOutputStream.java:80)
Thank you for your report. Can you please add steps to reproduce this issue? To be honest I didn't catch this issue. :) Is this exception thrown while user is trying to execute more than one test simultaneously?
Without requested information for long time - INVALID. We can't do anything in this case. Reporter, please add requested information and reopen issue. Thanks in advance.
Sorry for the delay, the notification emails dropped on the floor. As for steps to reproduce, there don't appear to be any notable steps -- just running our test build target (which currently explicitly names a series of tests in a junit tag) produces this behaviour. Running the same target from the command-line doesn't produce the same behaviour. No, I'm not running more than one test at a time. A colleague of mine gets similar errors (AssertionErrors in JUnitOutputReader), but in his case, they cause the test to fail, rather than to stall. He's also on OS X 10.5.x, FWIW. I think he's submitted the associated stack traces as well.
Sorry, this is not enough to reproduce the issue. Is it possible to attach your project or at least just a single problem class and corresponding test to localize the problem?
Without requested information for long time - WORKSFORME. We can't do anything in this case. Reporter, please add requested information and reopen issue. Thanks in advance.