There are some synchronazition issues in creating the IOContainer for ResultDisplayHandler; in certains cases
RDH#displayOuput gets called before the IOContainer has been created, causing this output not to be printed to the
output pane in the test results window. Also, sometimes no node is displayed either. This is easily reproducible in
Ruby (with MRI, probably because of the faster execution, no startup delay), but affects also the Java and other test
runners. Reproducbile e.g. with the following steps in Ruby:
1. create a new Ruby app
2. create a new test file
3. make the test output something and pass (and make sure it runs fast) => no output displayed, no node for the test
(You may need to close the window and run the test a few times to see the problem)
I have a fix for this, so assigning for myself. I think this needs to be fixed for 6.7 FCS.
Fixed in http://hg.netbeans.org/ruby-main/rev/bd9a8a4b4b46 - Andrey, can you please review the fix? As agreed with QA
I'm increasing the priority to P1 (based on the fact that this is not Ruby specific, can happen in Java/PHP/Python as
Fix verified in ruby continuous build by QE.
Integrated into 'main-golden', will be available in build *200905260201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
User: Erno Mononen <email@example.com>
Log: #165947: No output for tests in the test results window
I'd need to get the fix reviewed soon so that I can send an email to the reviewers alias (as per http://
wiki.netbeans.org/NB67HighResistance). Andrey, can you please do that? Thanks.
keep opened for 6.7
It looks fine for me.
this is already fixed in release67, isn't it ?
Yes, I apparently forgot to add the keyword - thanks.
... and mark issue as FIXED
Verified in release67 by QE.