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.
I am currently working on a project which I have put a *lot* of diagnostic logging into. Whenever I run tests, the output window handles this fine, but there is a long hang during which the IDE is unresponsive, just before the test results window appears. I'm guessing it is due to parsing of the output or something. I will attach the project.
Created attachment 24290 [details] Project w/ logging - Unzip into contrib/misc
Tim, the project you attached depends on another project "numeric_collections". Could you send me that project, please? (You might prefer sending it via a private e-mail.) Thanks.
It's in contrib/misc. Some stuff I factored out of core/output2.
Will be fixed.
Fixed together with bug #69755 ("JUnit results window does not display results until all tests finish"), in the trunk. Added, removed and modified files: junit/src/org/netbeans/modules/junit/output: ResultPanelTree.java (1.5) Manager.java (1.6) ResultDisplayHandler.java (1.2) XmlOutputParser.java (1.6) RootNode.java (1.1 - new file) TestsuiteNodeChildren.java (1.1 - new file) ReportNodeChildren.java (deleted - last rev. 1.2) Bundle.properties (1.10) ResultWindow.java (1.9) OutputUtils.java (1.2) JUnitAntLogger.java (1.10) TestcaseNodeChildren.java (deleted - last rev. 1.1) RootNodeChildren.java (1.1 - new file) ResultPanelOutput.java (1.4) TestcaseNode.java (deleted - last revision 1.1) JUnitOutputReader.java (1.11) TestsuiteNode.java (1.1 - new file) ResultTreeView.java (1.7) Report.java (1.9) ReportNode.java (deleted - last revision 1.4) Diff: http://junit.netbeans.org/source/browse/junit/src/org/netbeans/modules/junit/output/ResultPanelTree.java?r1=1.4&r2=1.5&diff_format=u http://junit.netbeans.org/source/browse/junit/src/org/netbeans/modules/junit/output/Manager.java?r1=1.5&r2=1.6&diff_format=u http://junit.netbeans.org/source/browse/junit/src/org/netbeans/modules/junit/output/ResultDisplayHandler.java?r1=1.1&r2=1.2&diff_format=u http://junit.netbeans.org/source/browse/junit/src/org/netbeans/modules/junit/output/XmlOutputParser.java?r1=1.5&r2=1.6&diff_format=u http://junit.netbeans.org/source/browse/junit/src/org/netbeans/modules/junit/output/RootNode.java?rev=1.1&content-type=text/vnd.viewcvs-markup http://junit.netbeans.org/source/browse/junit/src/org/netbeans/modules/junit/output/TestsuiteNodeChildren.java?rev=1.1&content-type=text/vnd.viewcvs-markup http://junit.netbeans.org/source/browse/junit/src/org/netbeans/modules/junit/output/Bundle.properties?r1=1.9&r2=1.10&diff_format=u http://junit.netbeans.org/source/browse/junit/src/org/netbeans/modules/junit/output/ResultWindow.java?r1=1.8&r2=1.9&diff_format=u http://junit.netbeans.org/source/browse/junit/src/org/netbeans/modules/junit/output/OutputUtils.java?r1=1.1&r2=1.2&diff_format=u http://junit.netbeans.org/source/browse/junit/src/org/netbeans/modules/junit/output/JUnitAntLogger.java?r1=1.9&r2=1.10&diff_format=u http://junit.netbeans.org/source/browse/junit/src/org/netbeans/modules/junit/output/RootNodeChildren.java?rev=1.1&content-type=text/vnd.viewcvs-markup http://junit.netbeans.org/source/browse/junit/src/org/netbeans/modules/junit/output/ResultPanelOutput.java?r1=1.3&r2=1.4&diff_format=u http://junit.netbeans.org/source/browse/junit/src/org/netbeans/modules/junit/output/JUnitOutputReader.java?r1=1.10&r2=1.11&diff_format=u http://junit.netbeans.org/source/browse/junit/src/org/netbeans/modules/junit/output/TestsuiteNode.java?rev=1.1&content-type=text/vnd.viewcvs-markup http://junit.netbeans.org/source/browse/junit/src/org/netbeans/modules/junit/output/ResultTreeView.java?r1=1.6&r2=1.7&diff_format=u http://junit.netbeans.org/source/browse/junit/src/org/netbeans/modules/junit/output/Report.java?r1=1.8&r2=1.9&diff_format=u
FYI, if you aren't doing so already, it would be a relatively small change I think to core/output2 to enable you to get your own output window component that you can write output to, without it needing to be in the output window. Standard Swing text support doesn't scale well at all (it does okay if the data is never modified, but it will use a lot of heap); the output window keeps its data off the java heap and is designed to scale to vast amounts of output (when I was developing it, I tested it with 400Mb of text, wrapped, and the performance was very good). Might be worth a try.
No, I haven't tried yet. Thank you for the tip. Are you a developer of core/output2?