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: | AssertionError: o.n.m.junit.GoToOppositeAction.isEnabled in automated tests | ||
|---|---|---|---|
| Product: | java | Reporter: | Marian Mirilovic <mmirilovic> |
| Component: | JUnit | Assignee: | Marian Petras <mpetras> |
| Status: | CLOSED WONTFIX | ||
| Severity: | blocker | Keywords: | T9Y |
| Priority: | P4 | ||
| Version: | 6.x | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | http://beetle.czech.sun.com/automatedtests/xtest/netbeans_dev/200707171200/qa-functional_stable/qa-t4u-lin1_1/testrun_070718-052059/testbag_15/htmlresults/suites/TEST-gui.javahelp.JavaHelpDialogTest.html#testHelpF1 | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Attachments: | AssertionError - stack trace | ||
|
Description
Marian Mirilovic
2007-07-18 08:26:32 UTC
Created attachment 45284 [details]
AssertionError - stack trace
It seems that this has the same cause as bug #90590. The method from which the AssertionError is thrown, is:
@Override
public boolean isEnabled() {
assert EventQueue.isDispatchThread();
return checkDirection() != null;
}
It is the assertion that EventQueue.isDispatchThread() what fails. But from the callstack, it is apparent that the
method was actually called from an event-dispatching thread.
Most probably this is caused by some of the following JDK bugs:
http://bugs.sun.com/view_bug.do?bug_id=6542185 - "Threading issues with java.awt.EventQueue.push/pop"
http://bugs.sun.com/view_bug.do?bug_id=6424157 - "java.awt.EventQueue push/pop might cause threading issues"
http://bugs.sun.com/view_bug.do?bug_id=6553239 - "one more threading problem with EventQueue.pop()"
This bug is really hard to reproduce and it does not happen in recent builds. It also happened only during automatic
tests, not during real work with NetBeans, so I lower the priority to P4.
This is caused by a JDK bug so I mark this bug as WONTFIX, with an appropriate JDK bug reference in the status
whiteboard field.
v/c |