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.

Bug 138019

Summary: test runner window doesn't always show the results of the latest test
Product: ruby Reporter: jamespb <jamespb>
Component: TestingAssignee: Erno Mononen <emononen>
Status: VERIFIED FIXED    
Severity: blocker CC: mschovanek, pjiricka
Priority: P1    
Version: 6.x   
Hardware: All   
OS: All   
Issue Type: DEFECT Exception Reporter:
Attachments: this is the problem state it goes back to over and over, no matter how often I change the pane sizes
After hitting run again, the test runner doesn't pick up the test output.
screencast of the problem

Description jamespb 2008-06-23 19:33:55 UTC
If I have the test runner pane set to the bottom part of the window, then every time I run the tests it resizes the left
pane to be tiny.  I'll attach screenshots.

version:
changeset:   85655:f26409083542
tag:         tip
parent:      85653:81b260e9326f
parent:      85654:d2b4950396b7
user:        Rohan Ranade <rohanranade@netbeans.org>
date:        Mon Jun 23 16:27:47 2008 +0530
summary:     Automated merge with http://hg.netbeans.org/main
Comment 1 jamespb 2008-06-23 19:34:18 UTC
Product Version: NetBeans IDE Dev (Build 080621)
Java: 1.6.0_03; Java HotSpot(TM) Client VM 1.6.0_03-b05
System: Linux version 2.6.22-14-generic running on i386; UTF-8; en_US (nb)
Userdir: /home/james/.netbeans/dev
Comment 2 jamespb 2008-06-23 19:36:42 UTC
Created attachment 63288 [details]
this is the problem state it goes back to over and over, no matter how often I change the pane sizes
Comment 3 jamespb 2008-06-23 19:39:20 UTC
The more I run this, the more I think something else is wrong.

This time, when I hit shift-F6 to run the tests, I got no output.  I see Running... in the left pane, and the progress
bar in the lower right corner is gone, so nothing is actually running.  There were no changes to the test itself, should
have been the same output (with multiple failures) as before.
Comment 4 jamespb 2008-06-23 19:40:52 UTC
Created attachment 63289 [details]
After hitting run again, the test runner doesn't pick up the test output.
Comment 5 jamespb 2008-06-23 20:30:08 UTC
(I just changed the title - I think this is a more serious problem than just resizing the window)

It looks like the test runner isn't always updating its results when a test finishes.  If I run a test ten times, I'll
frequently get runs where all it displays is the "Running..." message.  Occasionally it looks like I'm seeing results
from a previous run as well.
Comment 6 jamespb 2008-06-23 20:53:48 UTC
Created attachment 63294 [details]
screencast of the problem
Comment 7 Erno Mononen 2008-06-23 21:41:09 UTC
Thanks for the screencast. I'll look into this, seems to be a rather serious issue (probably will raise to P1). Will 
fix for M1 in any case. 
Comment 8 Erno Mononen 2008-06-24 16:43:17 UTC
I'm upgrading this to P1, I think this should be pushed to the recently created M1 clone too. I pushed the fix to main, 
changeset #90e3bfa3f7c4. Martine, do you agree that this can be ported to the M1 clone? Please verify first though, the 
change wasn't entirely trivial.
Comment 9 jamespb 2008-06-24 18:26:37 UTC
I'm running NetBeans Ruby up to change 85923:68e68ccd7d05.  Haven't had any problems so far.

As a ruby on rails user, I'd say NetBeans isn't usable without this fix (or without removing the testrunner jar completely).
Comment 10 Erno Mononen 2008-06-24 19:27:42 UTC
Forgot to raise to P1.
Comment 11 jamespb 2008-06-24 20:21:06 UTC
It's still not completely fixed - occasionally I get the behavior where the tests run to completion, and nothing
displays in the test runner other than "Running..."

I don't think this is a P1 though - should I open another bug to track it?
Comment 12 Erno Mononen 2008-06-24 21:15:46 UTC
There is already issue 135681 for similar behaviour, its priority may need to be raised if that happens often enough. 
I've seen it fairly rarely so far, had a quick look at it but wasn't able track down the root cause (since I wasn't 
successful in reproducing that while debugging). Just today I checked in some additional logging that should help in 
finding the culprit, so if you keep running into that issue, please attach the log file with the ruby logging enabled 
as described at http://wiki.netbeans.org/FaqRubyNBLogging (probably already familiar to you).
Comment 13 Martin Schovanek 2008-06-27 12:47:42 UTC
Verified in trunk #2497 build. Erno transplant it please into M1.
Comment 14 Erno Mononen 2008-06-27 14:05:00 UTC
Transplanted as 0c52ecba818b.
Comment 15 Quality Engineering 2008-06-27 16:15:07 UTC
Integrated into 'main-golden', available in NB_Trunk_Production #285 build
Changeset: http://hg.netbeans.org/main/rev/90e3bfa3f7c4
User: Erno Mononen <emononen@netbeans.org>
Log: #138019: test runner window doesn't always show the results of the latest test
+ more logging
+ synchronization improvements