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.
| Summary: | waitScanFinished never finishes in automated tests | ||
|---|---|---|---|
| Product: | java | Reporter: | Marian Mirilovic <mmirilovic> |
| Component: | Unsupported | Assignee: | Martin Matula <mmatula> |
| Status: | CLOSED FIXED | ||
| Severity: | blocker | CC: | issues, issues, jchalupa |
| Priority: | P1 | Keywords: | T9Y |
| Version: | 4.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Attachments: |
thread-dump when time expired
thread-dump a 3-5 minutes after opening projects |
||
Created attachment 16729 [details]
thread-dump when time expired
Created attachment 16730 [details]
thread-dump a 3-5 minutes after opening projects
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 *** 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? 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. 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 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. 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 verified in [nb_dev](200408111800) verified in Q-build 200408121535 |
[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 !!!