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 153526 - Call to findCompletionJList caused assertion error.
Summary: Call to findCompletionJList caused assertion error.
Status: RESOLVED WORKSFORME
Alias: None
Product: qa
Classification: Unclassified
Component: Jellytools (show other bugs)
Version: 6.x
Hardware: All All
: P1 blocker (vote)
Assignee: issues@qa
URL:
Keywords:
: 129819 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-11-20 11:07 UTC by Michael Nazarov
Modified: 2009-04-14 13:23 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 Michael Nazarov 2008-11-20 11:07:49 UTC 
P1 as it affects commit validation tests for PHP area of NB trunk.

Our tests test code completion lists. After some changes announced as
http://hg.netbeans.org/main?cmd=changeset;node=61ad9681ecc6
we even can't create CompletionJListOperator object because call to
"new CompletionJListOperator( )" brings followed exception:

Error Message

ListModel methods should be called form AWT event thread

Stacktrace

java.lang.AssertionError: ListModel methods should be called form AWT event thread
	at org.netbeans.modules.editor.completion.LazyListModel.initialize(LazyListModel.java:297)
	at org.netbeans.modules.editor.completion.LazyListModel.getSize(LazyListModel.java:409)
	at org.netbeans.jellytools.modules.editor.CompletionJListOperator.getCompletionItems(CompletionJListOperator.java:103)
	at org.netbeans.jellytools.modules.editor.CompletionJListOperator.access$100(CompletionJListOperator.java:78)
	at org.netbeans.jellytools.modules.editor.CompletionJListOperator$1.actionProduced(CompletionJListOperator.java:161)
	at org.netbeans.jemmy.Waiter.checkActionProduced(Waiter.java:271)
	at org.netbeans.jemmy.Waiter.waitAction(Waiter.java:164)
	at org.netbeans.jellytools.modules.editor.CompletionJListOperator.waitFor(CompletionJListOperator.java:192)
	at org.netbeans.jellytools.modules.editor.CompletionJListOperator.findCompletionJList(CompletionJListOperator.java:114)
	at org.netbeans.jellytools.modules.editor.CompletionJListOperator.<init>(CompletionJListOperator.java:88)
	at org.netbeans.test.php.Commit.GetCompletion(Commit.java:206)
	at org.netbeans.test.php.Commit.TestPHPFile(Commit.java:357)
	at org.netbeans.test.php.Commit.ManipulateIndexPHP(Commit.java:588)
	at org.netbeans.jellytools.JellyTestCase.runTest(JellyTestCase.java:184)
	at org.netbeans.junit.NbTestCase.access$200(NbTestCase.java:84)
	at org.netbeans.junit.NbTestCase$2.doSomething(NbTestCase.java:332)
	at org.netbeans.junit.NbTestCase$1Guard.run(NbTestCase.java:269)
	at org.netbeans.junit.NbTestCase.runBare(NbTestCase.java:348)
	at org.netbeans.jellytools.JellyTestCase.runBare(JellyTestCase.java:151)
	at org.netbeans.junit.NbTestCase.run(NbTestCase.java:209)
	at org.netbeans.junit.NbModuleSuite$S.runInRuntimeContainer(NbModuleSuite.java:522)
	at org.netbeans.junit.NbModuleSuite$S.run(NbModuleSuite.java:407)
Comment 1 Dusan Balek 2008-11-27 08:09:19 UTC 
*** Issue 129819 has been marked as a duplicate of this issue. ***
Comment 2 Vojtech Sigler 2009-04-14 13:23:10 UTC 
Tested CompletionJListOperator and all seems to work fine. I was unable to reproduce this issue, so I'm closing this
issue as WORKSFORME.