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 47071 - waitScanFinished never finishes in automated tests
Summary: waitScanFinished never finishes in automated tests
Status: CLOSED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 4.x
Hardware: All All
: P1 blocker (vote)
Assignee: Martin Matula
URL:
Keywords: T9Y
Depends on:
Blocks:
 
Reported: 2004-08-11 07:55 UTC by Marian Mirilovic
Modified: 2007-09-26 09:14 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
thread-dump when time expired (8.23 KB, text/plain)
2004-08-11 07:57 UTC, Marian Mirilovic 		Details
thread-dump a 3-5 minutes after opening projects (17.46 KB, text/plain)
2004-08-11 07:58 UTC, Marian Mirilovic 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Marian Mirilovic 2004-08-11 07:55:49 UTC 
[nb_dev](200408101800), [jdk1.5.0](b62)

Performance tests show not finished scan after
openinng projects by 
org.netbeans.junit.ide.ProjectSupport.openProject("My
Project")

Thread-dump shows 
"Thread-4" prio=10 tid=0x006a7298 nid=0x23 waiting
on condition [0xf1f7f000..0xf1f7fbc8]
at java.lang.Thread.sleep(Native Method)
at
org.netbeans.modules.javacore.JMManager.waitScanFinished(JMManager.java:471)
at
org.netbeans.xtest.plugin.ide.MainWithProjects.openProject(MainWithProjects.java:85)


scan doesn't finish in 40 minutes :
Tue Aug 10 21:41:27 CEST 2004: just starting.
Tue Aug 10 22:21:27 CEST 2004: time-out expired -
interrupting! ***

!!! there is no Scan dialog on the screenshots !!!
Comment 1 Marian Mirilovic 2004-08-11 07:57:16 UTC 
Created attachment 16729 [details]
thread-dump when time expired
Comment 2 Marian Mirilovic 2004-08-11 07:58:09 UTC 
Created attachment 16730 [details]
thread-dump a 3-5 minutes after opening projects
Comment 3 psuk 2004-08-11 12:00:22 UTC 
Looking into thread dump, there is no "Scanning Queue", so scan has
finished already, but it looks like that Scan dialog was not painted
at all (see Issue 47072)


*** This issue has been marked as a duplicate of 47072 ***
Comment 4 Jan Chalupa 2004-08-11 12:23:18 UTC 
To psuk: is there a clear evidence that this issue is a duplicate of
issue #47072? The symptoms are very different. #47072 is about
extremely bad user experience. #47071 is about specific state not
being signalled properly, which causes the test infrastructure to fail.

Could this be revisited and explained in more detail please?
Comment 5 psuk 2004-08-11 14:26:42 UTC 
The problem is not in scanning, the root cause is in waitScanFinished
method that calls isProgressOpened.
isProgressOpened sets progressOpened to true.
isProgressOpened is called again from refreshCodeBases and as a
result, the progress dialog is not opened at all.
Comment 6 Martin Matula 2004-08-11 15:21:42 UTC 
Fixed.

Checking in src/org/netbeans/modules/javacore/JMManager.java;
/cvs/java/javacore/src/org/netbeans/modules/javacore/JMManager.java,v
 <--  JMManager.java
new revision: 1.45; previous revision: 1.44
done
Comment 7 Marian Mirilovic 2004-08-11 16:47:57 UTC 
This issue is pointed out as Q-build stopper 
http://qa.netbeans.org/q-builds/Q-build-report-200408101800.html
and must be fixed in QBE200408101800 branch too.

Please, solve it ASAP , we'll plan release Beta 1 based on this
Q-build next week.
Comment 8 Martin Matula 2004-08-11 17:47:32 UTC 
Done.

Checking in src/org/netbeans/modules/javacore/JMManager.java;
/cvs/java/javacore/src/org/netbeans/modules/javacore/JMManager.java,v
 <--  JMManager.java
new revision: 1.43.2.1; previous revision: 1.43
done
Comment 9 Marian Mirilovic 2004-08-12 14:39:31 UTC 
verified in [nb_dev](200408111800)
Comment 10 Marian Mirilovic 2004-08-13 06:47:18 UTC 
verified in Q-build 200408121535